Skip to main content
Glama

Check several VAT IDs

check_vat_ids
Read-onlyIdempotent

Checks up to 20 EU VAT IDs and/or Swiss UIDs live in the official registers. Returns one result per number in the same order, plus a summary count. Duplicates are looked up once.

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

Input Schema

NameRequiredDescriptionDefault
vat_idsYes1 to 20 VAT IDs or Swiss UIDs, each with country prefix.
with_receiptNoOptional, default false. Set true only when the user asks for a signed receipt of this check for their files.
requester_vat_idNoOptional: the user's OWN EU VAT ID. If given, VIES returns a consultation number as official proof of the check. Only pass it when the user provided their own VAT ID for this purpose.

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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description still adds real value beyond them: result ordering matches input order, a summary count is included, and duplicates are only looked up once — behavior an agent cannot infer from the annotations.

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 limits, then the return shape and the dedup rule. No filler or redundancy.

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 usefully states that results come back one-per-input in order plus a summary count. It stops short of describing what each result contains (validity flag, registered name/address) or how malformed or non-registered numbers appear, which an agent would need to interpret responses fully.

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 schema already explains the country-prefix requirement, the 1–20 bound, and when to use with_receipt and requester_vat_id. The description only restates the 20-item limit, adding nothing new about the two optional parameters, so 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 ('Checks'), resource ('EU VAT IDs and/or Swiss UIDs'), and scope ('up to 20 ... live in the official registers'). The batch limit plus 'one result per number' clearly separates it from the singular check_vat_id sibling without needing to name it.

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?

'Live in the official registers' implies this is for real registry lookups rather than format checks, which hints at the split from validate_vat_format. However, no sibling is named and there is no explicit when-to-use or when-not-to-use guidance for choosing between this and check_vat_id.

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