Skip to main content
Glama

AstraNL Dutch counterparty check

verify_astranl

Read-onlyIdempotent

Read receipts confirm which read was served when and through which door, with current or expired status and optional answer_sha256 match; content is not stored and is not a quote, price guarantee or proof of delivery. Verify supported AstraNL references without a key: ASTRA-A/R/C, alk_, att_/atr_ and RCPT-n. Checks vary by kind: agreement certificates use payload hash, chain link and server-side HMAC; ingress receipts are unsigned. Other signed records expose Ed25519 signature, Merkle inclusion where available, recomputed live, and claim (what exactly is attested, by whom, from which source, when, under which method, with which validity limits and current status VALID/EXPIRED/REVOKED/UNKNOWN). Integrity never implies the claim is true for your purpose; you apply your own acceptance rules. Tells you when to re-verify and how to consume a VALID receipt for a next action. Read-only, deterministic, no model in the path.

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": "verify_astranl"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesAny AstraNL reference: action receipt ASTRA-A-..., policy receipt ASTRA-R-..., consumption or agreement certificate ASTRA-C-..., log event alk_..., attestation att_/atr_..., ingress receipt RCPT-n
answer_sha256No

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / receipt
      Removed value: -{
      -  "default": false,
      -  "type": "boolean"
      -}
  2. Changed2 schema fields changed
    • addedInput schema / properties / answer_sha256
      Added value: +{
      +  "pattern": "^[0-9a-f]{64}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / receipt
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / ref / description
      Previous value: -"Any AstraNL reference: action receipt ASTRA-A-..., policy receipt ASTRA-R-..., consumption ASTRA-C-..., log event alk_..., attestation att_/atr_..., ingress receipt RCPT-n"New value: +"Any AstraNL reference: action receipt ASTRA-A-..., policy receipt ASTRA-R-..., consumption or agreement certificate ASTRA-C-..., log event alk_..., attestation att_/atr_..., ingress receipt RCPT-n"
  4. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses important behavioral limits: content is not stored, receipts are not quotes or proof of delivery, ingress receipts are unsigned, and integrity does not imply the claim is true for the caller's purpose. It also explains that checks vary by reference kind and lists the verification evidence exposed, which is substantial transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is information-dense but poorly structured: it opens with a detailed explanation of read receipts before the main verification action, and several semicolon-separated clauses make it harder to scan. Most content is relevant, but the wall-of-text presentation reduces clarity.

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?

For a complex verification tool with no output schema, the description does a good job explaining what kinds of checks may be performed and what the returned claim/status information represents. It still lacks a concrete return shape, but the behavioral context is mostly sufficient for an agent to decide whether to call it.

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 schema already documents the ref parameter at length, but the description adds useful semantics by enumerating AstraNL reference families and by mentioning the optional answer_sha256 match. It does not fully explain when or why to supply answer_sha256, but it compensates for the partial schema coverage better than a bare restatement would.

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 clearly states the core action: 'Verify supported AstraNL references without a key,' and lists the supported reference kinds. It is specific about the resource and scope, though it does not explicitly differentiate itself from sibling verification tools.

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

Usage Guidelines3/5

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

Usage guidance is present but indirect: it says 'without a key,' notes that the caller must apply 'your own acceptance rules,' and promises to tell you 'when to re-verify and how to consume a VALID receipt.' However, it does not state concrete when-to-use conditions or name alternative tools such as commitment_verify.

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