Skip to main content
Glama

Validate VAT ID format

validate_vat_format
Read-onlyIdempotent

Offline check of format and check digit for up to 100 EU VAT IDs or Swiss UIDs, without contacting any register. Fast and unlimited. It cannot tell whether a number is registered; use check_vat_id for that.

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_ids": "<vat_ids>"
    },
    "name": "validate_vat_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
vat_idsYes1 to 100 VAT IDs or Swiss UIDs.
with_receiptNoOptional, default false. Set true only when the user asks for a signed receipt of this check for their files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / vat_ids / items / minLength
      Removed value: -1
    • 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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and no-network behavior are partly covered. The description reinforces this with concrete consequences — offline, no register contacted, unlimited use, and the crucial limitation that format validity does not imply registration. It stops short of describing what a result looks like, since there is no output schema.

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 capability, then the cost profile, then the limitation and the rerouting alternative. No redundant phrasing or 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?

For a two-parameter read-only validator the description covers purpose, scope, cost, and the key limitation. The one missing element is the return shape — e.g. whether per-ID validity and error reasons come back — which matters here because no output schema exists.

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% and both parameters are documented in the schema, including the with_receipt conditional and the 1–100 array bounds. The description only echoes the batch limit and ID types already encoded in maxItems and item descriptions, adding no new parameter meaning beyond the schema — baseline 3.

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 — offline format and check-digit validation of EU VAT IDs and Swiss UIDs — plus scope limits (up to 100, no register contact). It explicitly contrasts itself with the register-checking sibling check_vat_id, 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-not ('It cannot tell whether a number is registered') and names the alternative to use instead ('use check_vat_id for that'). The 'Fast and unlimited' note further signals it is the cheap first-pass option, leaving nothing to inference.

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