Skip to main content
Glama

AstraNL Coordination Protocol

coordination_contract

Read-onlyIdempotent

Read the published six-step coordination contract, refusals and boundaries verbatim. No account or project. AstraNL never completes checkout, pays, fills seller forms or holds funds. Read only. For a digest receipt of this read, confirmable through any door, call read_with_receipt.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "coordination_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / receipt
      Removed value: -{
      -  "default": false,
      -  "type": "boolean"
      -}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond them by stating access needs (no account or project), that content is returned verbatim, and the substantive boundary that AstraNL never completes checkout, pays, fills seller forms, or holds funds. That boundary statement is genuinely useful scoping information an agent would not get from annotations.

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?

Four short sentences, front-loaded with what is read, followed by access constraints and the alternative. No filler. The sentence about AstraNL never completing checkout sits slightly apart from the read action and could momentarily read as tool behavior rather than contract content, a minor structural ambiguity.

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 input schema, no output schema, and triple-annotated safety hints, the description carries only what remains: what the tool returns (verbatim contract text), what access it needs (none), and where to go for a receipt. That is sufficient for an agent to call it confidently. A brief note on whether the contract is versioned or time-sensitive is the only meaningful omission.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is a 4. The description correctly implies no input is required by noting no account or project is needed.

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?

Uses a specific verb ("read") against a specific resource ("the published six-step coordination contract") and names the content returned: refusals and boundaries, verbatim. It is distinguishable from siblings because it describes static published policy text rather than a lookup or action. It falls short of 5 only because the domain term "coordination contract" is left undefined for an agent with no prior context.

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

Usage Guidelines4/5

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

Gives the precondition ("No account or project") and routing guidance for the adjacent tool: use read_with_receipt when a digest receipt is wanted. It explicitly frames itself as a standalone read. It does not state a when-not-to-use case, but the read-only nature and the named alternative cover the realistic selection decision.

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