Skip to main content
Glama

AstraNL Coordination Protocol

commitment_confirm

Idempotent

Answer an agreement using the private confirmation capability received from its issuer. The first valid answer stands; identical repeats return the same record. This records the holder answer only, not identity or performance. Never publish the capability. The issuer hands over certificate_id and capability, or a confirm link where ref is certificate_id and the part after #c= is capability. A disputed answer may include a reason of at most 300 characters.

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": {
      "certificate_id": "<certificate_id>",
      "capability": "<capability>",
      "decision": "<decision>"
    },
    "name": "commitment_confirm"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNo
reasonNo
decisionYes
capabilityYes
certificate_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations it discloses that the first valid answer wins and identical repeats return the same record, that only the holder's answer is recorded (not identity or performance), and that the capability must never be published. These are real behavioral and security facts an agent needs; it still does not describe the response payload.

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

Conciseness4/5

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

Sentences are short and front-loaded with the action, followed by idempotency, scope, security, and input-derivation details. Nothing is padded, though the ordering puts a security warning before the input-location explanation.

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

Completeness3/5

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

For a 5-parameter mutation tool with no output schema and 0% schema descriptions, the description covers the main flow well but leaves 'role' undefined and says nothing about what the returned record contains or how a disputed answer is surfaced. An agent can call it correctly in the common case but not fully.

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

Parameters4/5

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

Schema coverage is 0%, so the description carries the burden, and it explains how certificate_id and capability are obtained, including how to parse them out of a confirm link ('ref is certificate_id and the part after #c= is capability'). It also constrains reason to 300 characters for disputed answers, though the optional 'role' parameter is never explained.

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?

The description states a concrete verb and resource: 'Answer an agreement' using a specific confirmation capability, and scopes it ('records the holder answer only, not identity or performance'). That distinguishes it in substance from siblings like commitment_verify or commitment_attest, though it never names an alternative directly.

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?

It explains the precondition for use: the issuer must hand over certificate_id and capability (or a confirm link), which tells the agent where inputs come from. It gives no when-not guidance and no comparison to other commitment_* tools, leaving the selection with the caller.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources