Skip to main content
Glama

AstraNL Coordination Protocol

check_counterparty_nl

Read-onlyIdempotent

Check a Dutch or EU counterparty against official sources before your own next step, such as onboarding a supplier, paying an invoice or signing an order. Give the KvK number, the company name and the EU VAT number as your document states them. Returns verdicts, not register data: whether the KvK number has an active registration, whether the name matches a registered name, whether the VAT number is valid in VIES and whether its VIES name matches the register, EU sanctions list candidates, whether an insolvency case is published under the KvK number in the Dutch insolvency register, open questions and a check_id. Read-only, no key, no cost. AstraNL does not search the Dutch register by name; look a number up at kvk.nl. The check_id identifies this result for 48 hours. It does not prove who may sign for the company, who owns a bank account, solvency or reliability.

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

Input Schema

NameRequiredDescriptionDefault
cityNonot used; kept for compatibility, AstraNL does not search the register by name
purposeNooptional: the next action you are about to take, for example approve supplier or pay invoice
kvk_numberNoDutch KvK number, 8 digits, as printed on the invoice, quote or website
vat_numberNoEU VAT number with country prefix, for example NL810433941B01
company_nameNothe company name exactly as your document or contact states it

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, non-destructive and open-world, and the description still adds substantial context beyond them: no key, no cost, verdicts rather than register data, and a 48-hour lifetime for the returned check_id. It also discloses a hard behavioral limit (no name-based register search; use kvk.nl) that an agent could not infer from annotations or schema.

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 action, then the return payload, then the disclaimers, so an agent can stop reading early and still act. It is dense and long-sentenced, and the closing disclaimer partly overlaps the earlier "verdicts, not register data" framing, but the length is justified by the absence of an output schema.

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 explaining returns and does so item by item: registration status, name match, VIES validity and name match, sanctions candidates, insolvency publication, open questions, and check_id. It also covers cost, authentication, result lifetime, and the boundaries of what the verdict proves, leaving no material gap for correct invocation.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning: supply the KvK number, company name and EU VAT number exactly as the document states them, which frames the values as document transcriptions rather than normalized lookups. It also repeats the key constraint that name is matched against a registered name rather than used to search, reinforcing why `city` is inert.

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 a Dutch or EU counterparty against official sources, with concrete use cases (onboarding a supplier, paying an invoice, signing an order). It also sharply bounds scope by saying it returns verdicts, not register data, and that AstraNL does not search the register by name. It never names or contrasts the sibling tools (record_counterparty_check, verify_astranl), so differentiation is left to inference.

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 clear positive framing ("before your own next step") with three concrete example situations, and explicit limits on what the result does not establish (signing authority, bank account ownership, solvency, reliability). What is missing is routing guidance: nothing tells the agent when to use record_counterparty_check instead, or how this relates to verify_astranl.

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