Submit my availability or preference change
Requires mcp:self:write and current manage_own_scheduling_preferences. An ordinary change becomes an effective revision; one that conflicts with published commitments, contract minimums or unassessed impact stays pending_review. Never routed through manage_schedules.
Authorizations
Existing Atlas integration connection with explicit api:connect plus appropriate native domain grants. atlas_ingest_ and browser cookies are not accepted.
Headers
Selector within saved grants and current issuer authority; never grants authority.
Stable native operation key. Reuse it as request_key through MCP; a changed body under the same key conflicts.
Body
Response
Native typed result.
Native typed outcome. Depending on the operation: records and effective revisions, issues with code, field path, severity and source references, applied constraints, soft preference effects, affected drafts and future published commitments with complete, missing or unsupported evidence, replayed for an exact retry and verified effect references. Authored availability, preference and pattern bodies round-trip unchanged.