macp-mcp

Official

Overview Schema Source Related Servers Discussions Admin

get_commitment

Read-onlyIdempotent

Retrieve the binding Commitment payload and its recomputable hash for a resolved MACP session; returns found=false while the session is still open.

Instructions

Return a resolved session's binding Commitment and its RFC-MACP-0013 hash.

found is false while the session is still open. payload_b64 is the exact Commitment payload bytes the runtime recorded; commitment_hash is computed over them.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "get_commitment"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes	The MACP session id (from start_session).

Output Schema

Name	Required	Description	Default
`found`	Yes
`state`	Yes
`sender`	No
`commitment`	No
`hash_label`	No
`message_id`	No
`session_id`	Yes
`payload_b64`	No
`commitment_hash`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 27, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and repeatability are covered. The description adds meaningful state behavior beyond that: a not-found result while the session is open, and the fact that payload_b64 is the exact recorded byte sequence while commitment_hash is computed over those bytes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short lines with zero waste: purpose first, then the not-found condition, then the return-field semantics. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even though an output schema exists, the description clarifies the otherwise ambiguous `found` flag and the relationship between payload_b64 and commitment_hash. Combined with annotations covering safety and the schema covering the parameter, an agent has everything needed to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single session_id parameter is fully documented in the schema. The description adds no syntax, format, or meaning beyond what the schema provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: returns a resolved session's binding Commitment plus its RFC-MACP-0013 hash. It is clearly distinct from siblings like commit or verify, though it never explicitly names get_session as the alternative for non-commitment data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The clause 'found is false while the session is still open' implies the tool should be called after a session resolves, which is useful usage context. However, it never states when to use this versus get_session or verify, and no exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server