Skip to main content
Glama

verify_eu_vat_vies

Read-onlyIdempotent

Check one country-prefixed VAT number against the European Commission’s live VIES service. Read status as VALID, INVALID or UNKNOWN. A registry outage is inconclusive. Use check_czech_company_kyb for Czech tax reliability or published accounts.

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": "<vat>"
    },
    "name": "verify_eu_vat_vies"
  }
}

Input Schema

NameRequiredDescriptionDefault
vatYesEU VAT number with country prefix, e.g. CZ00094943

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so safety is covered; the description adds the important behavioral fact that this is a live registry call whose outage yields an inconclusive UNKNOWN rather than a failure. Without an output schema, disclosing the VALID/INVALID/UNKNOWN status vocabulary is meaningful added context. It does not mention rate limits or retry behavior for live lookups.

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 short sentences, front-loaded with the core action and scoped resource, then result semantics, then sibling routing. Nothing is redundant with the title or padded.

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 single-parameter lookup with no output schema, the description supplies what the schema cannot: the return status vocabulary and the meaning of an outage. It leaves minor gaps such as handling of malformed or non-EU input, but an agent has enough to call it correctly.

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 description coverage is 100% and the single parameter already carries its own description with an example (CZ00094943). The description's 'country-prefixed' repeats the schema constraint rather than adding new semantics, so the baseline 3 applies.

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 and resource (check a country-prefixed VAT number) against a named authority (European Commission's live VIES service), and scopes it to one number at a time. The final sentence names the sibling tool check_czech_company_kyb, so an agent can distinguish the two without opening either schema.

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?

Explicitly routes the agent away from this tool for Czech tax reliability or published accounts, pointing at check_czech_company_kyb. It also implicitly limits the scope to a single EU VAT number via 'one country-prefixed VAT number'. It does not state when a VIES check is the wrong choice versus verify_iban or other siblings, so it stops short of a full when/when-not rule set.

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