Skip to main content
Glama

AstraNL Coordination Protocol

check_material

Read-onlyIdempotent

Check one building material in live Dutch store reality with ONE read-only call. Exact identity only: a GTIN with valid check digit, a store variant or the exact partner feed link; plain words return candidates you can check exactly next. Returns every offer of the same trade item with price incl. VAT, stock and read time per store (Bouwmaat, Hubo, Houtdirect through UCP search; partner shop feeds), the identical GTIN at other stores (verdict DIRECT_SUBSTITUTE, the only substitute named), the cheapest available offer, per source status and a sha256 digest. Limits: seller prices at read time, not a quote or delivery promise; delivery costs not included; NOT_FOUND covers only the sources listed. Never orders, pays or contacts anyone.

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": {
      "ref": "<ref>"
    },
    "name": "check_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesa GTIN or EAN with valid check digit (e.g. 8710839100056), a Bouwmaat, Hubo or Houtdirect product link with ?variant=, a partner shop product link, store:variant (e.g. hubo:48564194312444), or plain words for candidates

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, yet the description still adds substantive behavior: the full return payload (offers with VAT-inclusive price, stock, read time per store, DIRECT_SUBSTITUTE verdict, cheapest available offer, per-source status, sha256 digest). It also discloses limits beyond annotations — prices at read time are not a quote, delivery costs excluded, and NOT_FOUND scoped only to listed sources — which is exactly the extra context annotations cannot carry.

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?

Front-loaded with the core action and scope, then input rules, then outputs, then limits — a logical order with no filler sentences. It is dense and parenthetical-heavy ('Bouwmaat, Hubo, Houtdirect through UCP search; partner shop feeds'), which slightly taxes scanning but every clause carries information.

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?

There is no output schema, so the description must describe returns — and it does, itemizing offers, verdicts, cheapest offer and digest. Combined with explicit limits and a no-side-effects statement, an agent has everything needed to call it correctly and interpret the result.

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 100% and the single parameter already documents the accepted formats, so the baseline is 3. The description still adds real meaning: the distinction between exact identifiers (GTIN with valid check digit, store variant, partner feed link) that resolve directly and plain words that yield candidates, plus the fact that only DIRECT_SUBSTITUTE is a valid substitute verdict.

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 ('Check one building material in live Dutch store reality') plus the scope of a single read-only call, which is immediately actionable. It does not name any sibling (e.g. find_offers) as the alternative, so the agent must infer the boundary rather than being told it.

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?

'Exact identity only' with the enumerated accepted forms, and 'plain words return candidates you can check exactly next', gives clear conditions for how to invoke it and what happens when you don't have an exact key. 'Never orders, pays or contacts anyone' sets a negative boundary, but no named sibling is offered as the alternative for offer search or for non-exact lookups.

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