Skip to main content
Glama

AstraNL Coordination Protocol

commitment_verify

Read-onlyIdempotent

Verify an agreement certificate by ID, up to 40 characters. Returns the verification service verdict unchanged. A genuine certificate does not guarantee performance. It also shows whether the other party confirmed or disputed: counterparty.state is PENDING, CONFIRMED, DISPUTED, EXPIRED_UNANSWERED or NOT_OFFERED. Use this for agreement certificates; use verify_astranl for every other AstraNL reference.

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": {
      "id": "<id>"
    },
    "name": "commitment_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: the verdict is returned unchanged, a genuine certificate does not guarantee performance, and the possible counterparty.state values (PENDING, CONFIRMED, DISPUTED, EXPIRED_UNANSWERED, NOT_OFFERED) are enumerated. It does not say what happens for an unknown or malformed ID, which keeps it below a 5.

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?

The definition is front-loaded with the core action and routing rule, and every sentence carries information. The 'up to 40 characters' clause duplicates the schema constraint and is the one piece of low-value text.

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

Completeness4/5

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

With no output schema, the description usefully compensates by describing the return (verdict passed through unchanged plus counterparty state values) and by flagging the semantic caveat about certificates not guaranteeing performance. Only the error/not-found behavior is left unaddressed for this otherwise simple one-parameter tool.

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 description coverage is 0%, so the description carries the burden for the single id parameter, but it only restates the 40-character cap already encoded in maxLength and says nothing about the allowed character pattern or where an ID comes from. It adds only marginal meaning over the schema.

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

Purpose5/5

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

The description opens with a specific verb+resource ('Verify an agreement certificate by ID') and immediately differentiates itself from the sibling verify_astranl by scoping to agreement certificates only. An agent can choose between the two verification tools without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit routing rule: use this for agreement certificates, use verify_astranl for every other AstraNL reference. The alternative and the condition that selects it are both named outright.

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