Skip to main content
Glama

Registry Pages

Check a French VAT number in VIES

check_french_vat
Read-only

Checks the intra-EU VAT number of a French company (computed from its SIREN) against the European Commission VIES service. Returns valid or invalid, with the name and address VIES holds.

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": {
      "siren": "<siren>"
    },
    "name": "check_french_vat"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirenYes9-digit SIREN

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint and openWorldHint, so the description adds real value beyond them: it names the external authority (VIES), explains the VAT number is computed from the SIREN rather than supplied, and describes the return payload (valid/invalid plus VIES-held name and address). It does not mention VIES downtime or throttling behavior for an external call, which keeps it from a 5.

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 tight sentences: the operation and its external target first, the return shape second. No filler, no repetition of the title or schema.

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 one-parameter read tool with no output schema, the description covers input derivation, external dependency, and return values well. The only gap is undisclosed failure behavior when VIES is unavailable or the SIREN is malformed.

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% and documents the single 'siren' parameter, so the baseline is 3. The description goes further by clarifying that the SIREN is converted into a VAT number internally, telling the agent not to pass a VAT number directly — meaningful semantics beyond the schema.

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 ("Checks") plus the exact resource: the intra-EU VAT number of a French company, verified against the European Commission VIES service. It also explains the derivation from SIREN, which cleanly separates it from the sibling company-lookup tools.

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?

The context implies the use case (validating a VAT number for a French company) but never states when to pick this over the sibling lookups, nor any precondition such as needing a SIREN rather than a VAT number in hand. Usage is inferable but not spelled out.

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