MCP

A tool name is a capability id. Listing requires a valid key for a served workspace, so one definition and one key cover both calls. A human key is refused on the served surface.

POST /mcp
Authorization: Bearer trk_...

{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }

POST /mcp with tools/call. The arguments carry the payload and the scope. An extra argument key merges into the payload.

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "ticket6:readLedger",
    "arguments": {
      "program": "partner-2027",
      "relationship": "relationship:partner-2027:creator-1",
      "payload": {}
    }
  }
}

A refusal comes back as a JSON-RPC error whose message and data.code are the same name the API and the CLI return.

{
  "jsonrpc": "2.0",
  "id": 2,
  "error": { "code": -32000, "message": "WORKSPACE_REFUSED", "data": { "code": "WORKSPACE_REFUSED" } }
}

• An authentication failure uses code -32001.
• An unknown capability uses code -32602.
• Any other refusal uses code -32000.

21 of the 88 capabilities on the mcp surface are human gates. An agent that calls one creates an approval request and runs nothing. The tool is still listed, so the agent can see what it may ask for.

• campaigns:approveCampaign
• campaigns:launchCampaign
• campaigns:setupAdapter
• partners:grantAccess
• runtime:closeHeldEvent
• runtime:replayHeldEvent
• ticket13:commitCutover
• ticket15:assignReferralCode
• ticket4:acceptStandardTerms
• ticket6:activatePartnerOverride
• ticket6:activateRulebookVersion
• ticket6:approveCommission
• ticket6:approveCommissions
• ticket6:configureCommissionPolicy
• ticket6:rejectCommission
• ticket6:rejectCommissions
• ticket7:createManualCorrection
• ticket7:recordCarriedDebtRecovery
• ticket7:recordDisputeTransition
• ticket7:recordPayoutReceipt
• ticket7:recordStatementPayout

A row that is not served is declared in the code and not exposed by the runtime yet.

Generated from shyftai/trumpet at cbc30f1 by scripts/gen-reference.mjs.