commitments.resolve · Cortex MCP Docs

Description

Terminal transition. Per ADR-0021 §read-API Family C.

Input schema

Field	Type	Required	Description
`commitment_id`	`string`	yes	The commitment id.
`resolution_summary`	`string`	no	Optional summary of how it was resolved.

Output shape

typescript

{ ok: true }

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": "commitments.resolve", "arguments": { "commitment_id": "cmt_01H..." } }

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

{ "ok": true }

Errors this tool can return

Code	Meaning
`invalid_arguments`	Tool input failed Zod validation.
`unauthorized`	Missing or invalid bearer token.
`quota_exceeded`	Per-minute, daily call, or daily inference budget exceeded.
`not_found`	The requested resource (action_id, decision_id, counterparty_id, etc.) was not found.

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