Skip to main content
Glama
Sign In

Agent Data Tools: Company and VAT check

by io.github.Nutshell2000
OverviewDiscussionsAdmin

VAT number validation, EU VIES

vat_validate
Read-only

Check an EU VAT number against the European Commission's VIES service: valid or not, with the registered name and address where the member state shares them. Any spacing (SE556703748501, DE 123 456 789; EL or GR for Greece, XI for Northern Ireland). Or verify a business by name: found or not in the French, Swedish, Norwegian and Finnish registers. Use to check a B2B customer before invoicing without VAT, or to confirm a supplier. Example: vat=SE556703748501. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
vatNoVAT number with its 2-letter EU country prefix (give vat or name)
nameNoCompany name to verify instead of a VAT number: found or not in the FR, SE, NO and FI company registers
countryNoWith name: search only this register (FR, SE, NO or FI, or the country's name)

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?

Beyond readOnlyHint/destructiveHint/openWorldHint, the description discloses that results are partial by design ('where the member state shares them'), that name verification only covers FR, SE, NO and FI, and that each call costs $0.01 with the first 25 free and failed calls free. The note that 'repeats are not free' usefully explains the idempotentHint=false annotation.

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?

It is dense and front-loaded, leading with what the tool returns and following with input formatting and cost. The pricing and billing parenthesis is a bit crowded, but every sentence carries information an agent needs.

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 still explains return values for both modes (valid/not plus registered name and address; found/not for name search), input formats, coverage limits, and billing. Nothing material is missing 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 coverage is 100%, so the baseline is 3, but the description adds real value the schema lacks: tolerance for arbitrary spacing, alternate country codes (EL/GR for Greece, XI for Northern Ireland), and a worked example (vat=SE556703748501). The country parameter's role is only echoed, not extended.

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 verb and resource ('Check an EU VAT number against the European Commission's VIES service') and covers both operating modes: VAT lookup and business-name verification in the FR/SE/NO/FI registers. It is clearly distinct from generic company tools, though it never explicitly routes to siblings like fr_company or fi_company for register lookups.

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?

It states concrete use cases: 'check a B2B customer before invoicing without VAT, or to confirm a supplier.' That is clear contextual guidance, but there are no exclusions or named alternatives for when a different tool (e.g. company_enrichment) would be the better choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Data Tools: Company and VAT check toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources