Skip to main content
Glama

Check business partner

check_business_partner
Read-onlyIdempotent

One report on a business partner before invoicing or delivering: VAT ID (VIES or Swiss UID register), EORI customs number (the given one, or the VAT ID tried as EORI), Peppol e-invoicing reachability, and LEI with parent company. Each part names its own source and time and has its own status; a part whose source is down says so without affecting the others. No sanctions screening.

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": {
      "vat_id": "<vat_id>"
    },
    "name": "check_business_partner"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiNoOptional: the partner's LEI code.
eoriNoOptional: the partner's EORI number, if different from the VAT ID.
nameNoOptional: the partner's name, used for the LEI search when the register publishes none.
vat_idYesThe partner's VAT ID or Swiss UID.
with_receiptNoOptional, default false. Set true only when the user asks for a signed receipt of this check for their files.
requester_vat_idNoOptional: the user's OWN EU VAT ID. If given, VIES returns a consultation number as official proof of the check. Only pass it when the user provided their own VAT ID for this purpose.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / with_receipt
      Added value: +{
      +  "description": "Optional, default false. Set true only when the user asks for a signed receipt of this check for their files.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the bar is lower; the description still adds real value by disclosing graceful partial failure ("a part whose source is down says so without affecting the others"), per-part source and timestamp, and independent per-part status. It does not mention latency, cost, or any rate limiting across the multiple upstream registers.

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

Conciseness5/5

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

Two sentences, front-loaded with the deliverable and then the scope exclusion. Every clause carries information: the four check types, the source fallback rule, the partial-failure behavior, and the sanctions caveat, with no filler.

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?

With six parameters, no output schema, and an aggregation of four external registers, the description does the needed work by sketching the result shape (per-part source, time, and status) and the failure model. It is nearly complete; only the practical concerns of cost/latency when several registers are queried are unaddressed.

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?

Schema coverage is 100%, so all six parameters (including the with_receipt and requester_vat_id conditional semantics) are already documented in the schema. The description adds only one marginal detail beyond it: that EORI falls back to trying the VAT ID as an EORI number. Baseline 3 for a fully covered schema is appropriate.

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 names a specific deliverable (one consolidated report on a business partner) and enumerates exactly what it covers: VAT ID via VIES or Swiss UID, EORI, Peppol reachability, and LEI with parent company. This implicitly distinguishes it from the single-check siblings such as check_vat_id, check_eori, and find_peppol_participant, though no sibling is named explicitly.

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?

"Before invoicing or delivering" gives a concrete trigger for when to reach for this tool, and "No sanctions screening" scopes out a common assumption. It stops short of explicit routing advice such as 'use check_vat_id alone if you only need VAT validation', leaving the agent to infer the alternative from the sibling names.

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