Skip to main content
Glama

AgentSupply

Validate EU VAT number (VIES)

check_eu_vat
Read-only

Validate an EU VAT identification number against the European Commission's VIES service. Returns validity and, where disclosed by the member state, registered name and address. Live tool – free during the pilot, rate-limited.

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_number": "<vat_number>"
    },
    "name": "check_eu_vat"
  }
}

Input Schema

NameRequiredDescriptionDefault
vat_numberYesVAT number, with or without country prefix, e.g. DE123456789.
country_codeNoEU member state code, e.g. DE, FR, EL (Greece), XI (Northern Ireland). Optional if vat_number has a prefix.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful context beyond that: it discloses the return payload (validity plus member-state-disclosed name and address), flags the tool as live, and warns of rate limiting and pilot-stage free pricing. It does not state authentication/registration requirements or behavior on service downtime, which is a real gap for a live external call.

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?

Three sentences, front-loaded with what the tool does, then what it returns, then operational constraints. Every sentence carries distinct information with no repetition of the title or annotations.

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 no output schema, the description correctly compensates by describing return values, and both parameters are fully documented in schema. The remaining gap is operational failure modes (invalid format handling, VIES downtime, rate-limit thresholds) that matter for a live external dependency, plus the undisclosed auth/registration requirement.

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%, including the prefix-optional behavior for vat_number and the EL/XI country code examples, so the schema carries the parameter burden entirely. The description adds no parameter-level meaning beyond it, which is the expected baseline at full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (validate) and a specific resource (EU VAT identification number) and names the authoritative source, VIES. The resource itself cleanly separates it from siblings like lookup_lei or check_email_domain, so an agent can select it without opening the schema.

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 is only implied by the resource type: an agent infers it should call this when it has an EU VAT number to verify. There is no explicit when-to-use/when-not guidance and no named alternative for non-EU VAT or other identifier lookups among the siblings.

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