Skip to main content
Glama

AstraNL Coordination Protocol

ask_astranl

Read-onlyIdempotent

Turn a real-world task or question into a routing decision: whether AstraNL can help, which one tool to call, what to supply, what can and cannot be verified. No commitment, nothing created, no key. Also answers whether a physical task is feasible in the Netherlands.

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": {
      "question": "<question>"
    },
    "name": "ask_astranl"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesyour task or question in plain words, any language

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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=true, destructiveHint=false and idempotentHint=true, but the description still adds value by pre-empting side-effect worries in agent terms ("No commitment, nothing created, no key"), and "no key" discloses that no authentication is required — information absent from the annotations. "What can and cannot be verified" also signals that the answer may be bounded or incomplete, which is useful expectation-setting.

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 core verb and resource lead the sentence, and the colon-separated list of decision outputs is dense and scannable. The closing feasibility sentence is somewhat disjoint from the routing theme, and "No commitment, nothing created, no key" says the same thing three ways, but overall there is little wasted text.

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?

With no output schema, the description carries the full burden of describing the return, and it does so structurally: a routing decision composed of feasibility, a single recommended tool, required inputs, and verifiability limits. Combined with the read-only annotations and a fully documented single parameter, an agent has everything needed to call this correctly and interpret the result.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains that "question" is plain-language free text in any language with a 400-character cap. The description only echoes this indirectly via "what to supply" and adds no format, length, or content guidance beyond the schema — baseline 3.

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 specific transformation ("turn a real-world task or question into a routing decision") and enumerates the outputs of that decision: whether AstraNL can help, which single tool to call, what to supply, and what can be verified. That clearly distinguishes it as a dispatcher relative to action tools like create_task or commitment_attest, though the tacked-on second sentence about Dutch physical-task feasibility adds a second, partially separate purpose that softens the focus.

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?

Usage is strongly implied by the routing framing: this is the entry point an agent should hit when it has a raw task and doesn't yet know which of the family to call, and "which one tool to call" tells the agent the output is a pointer to a sibling. There is no explicit "use this instead of X" statement, no named alternative, and no stated exclusion, so it stops short of a 5.

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