action.schedule · Cortex MCP Docs

Description

Schedules a calendar event through the action engine. Same approval/trust semantics as `action.communicate` — send-class action, routed through gate.

Input schema

Field	Type	Required	Description
`title`	`string`	yes	Event title.
`when`	`string`	yes	ISO-8601 timestamp or natural language time.
`who`	`string`	no	Optional attendee or counterparty.
`context`	`string`	no	Optional scheduling context.

Output shape

typescript

{
  status: "success" | "pending_approval" | "error";
  decision_id?: string;
  message?: string;
  error?: string;
}

Example call

JSON-RPC tools/call request body (omit the JSON-RPC envelope when using an SDK; the SDK adds it for you):

jsontools/call params

{
  "name": "action.schedule",
  "arguments": {
    "title": "1:1 with Sarah",
    "when": "2026-06-03T14:00:00-04:00",
    "who": "entity_01HXSARAH",
    "context": "Monthly catch-up"
  }
}

Example response

Tool results are always wrapped as content[0].text with a stringified JSON body. The shape below is what you get back from JSON.parse(result.content[0].text):

jsonparsed result body

{
  "status": "pending_approval",
  "decision_id": "dec_01HXP9SCHED",
  "message": "Phase 0: Action Engine (Epic 7) not yet wired. This tool is structurally registered but deferred."
}

Errors this tool can return

Code	Meaning
`invalid_arguments`	Tool input failed Zod validation.
`unauthorized`	Missing or invalid bearer token.
`trust_insufficient`	The current autonomy level for this (action class × counterparty) is too low for direct execution.
`action_engine_error`	The action engine refused to enqueue the decision (downstream failure, transient).
`quota_exceeded`	Per-minute, daily call, or daily inference budget exceeded.

See the full error catalog for resolution steps on each code, plus the standard transport-layer responses (401, 429).