Skip to main content
Glama

AstraNL Coordination Protocol

ground_astranl

Read-onlyIdempotent

Get compact, source-linked real-world context for an LLM in ONE read-only call. Searches AstraNL public materials or tender records, or its protocol identity. Use source=public_tenders for tenders, materials for products; auto keeps domains separate. Returns record update times, fresh/stale/unknown labels, record disagreements, coverage gaps and ready-to-use context_text. Never books, contacts or pays anyone. Not a general web search: no match is not proof of absence; a cached price is not a quote. Optional astranl.reality-link.v2 profile checks exact source-record claims. It does not promote registry records to independently verified real-world facts. official.deadline on tender:TED-* records is checked live at the EU publisher (TED), budgeted and cached; unavailable means UNKNOWN.

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": {
      "query": "<query>"
    },
    "name": "ground_astranl"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesShort subject, product keywords or identifier; all product keyword groups must match.
claimsNov2 only. Each claim names a record id from a previous result, a predicate and the expected value.
sourceNov1: auto, materials, public_tenders, protocol_identity or all. v2 requires an explicit materials, public_tenders or protocol_identity.auto
protocolNoOmit for the v1 context call. Set to astranl.reality-link.v2 together with claims to check typed claims against source records.
budget_msNo
max_itemsNov1 only; v2 looks up at most 12 records and refuses max_items.
max_age_secondsNo

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 read-only, idempotent, closed-world and non-destructive, and the description still adds material behavior: it never books, contacts or pays anyone; no match is not proof of absence; a cached price is not a quote; registry records are not promoted to verified facts. It further discloses that official.deadline on tender:TED-* records is checked live at the EU publisher, budgeted and cached, with unavailable meaning UNKNOWN.

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 key capability and the read-only guarantee are front-loaded, and nearly every clause carries operational meaning (source routing, negative-result caveats, TED live check). It is dense to the point of being cramped into long sentences, which costs some readability but not correctness.

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 still enumerates what comes back: record update times, fresh/stale/unknown labels, record disagreements, coverage gaps and ready-to-use context_text. For a 7-parameter tool with two modes it covers the modes, the source routing and the trust caveats an agent needs before calling.

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?

Beyond the 71% schema coverage, the description explains source selection semantics and that v2 requires an explicit source, and it ties protocol=astranl.reality-link.v2 to the claims array. The schema covers max_items being v1-only, but the description reinforces the v1/v2 split that governs how several parameters interact.

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 verb and resource: get compact, source-linked real-world context in one read-only call, searching AstraNL public materials, tender records or protocol identity. It also scopes what it is not (a general web search). It never names a sibling tool such as ask_astranl or verify_astranl, so differentiation is left implicit.

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?

It gives concrete routing rules: source=public_tenders for tenders, materials for products, and auto keeps domains separate. It also states the v2 path (protocol plus claims) for checking exact source-record claims and warns against treating it as general web search. It stops short of explicit when-not-to-use-this-and-use-X-instead guidance against named alternatives.

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