Skip to main content
Glama

Validate a Swiss VAT number

validate_vat_number
Read-only

Validate Swiss VAT (MWST/TVA/IVA) numbers against the federal VAT register, returning active status and optional holder name, address, and VAT entry date for supplier and invoice checks.

Instructions

Check whether a Swiss VAT number (MWST/TVA/IVA) is valid and active in the federal VAT register via the UID register, e.g. 'CHE-107.028.276 MWST', 'CHE107028276TVA' or '107028276'. Returns valid true/false, the normalised VAT number and (with include_details) the holder's name, address and VAT entry date; use it for supplier/invoice checks.

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_number": "<vat_number>"
    },
    "name": "validate_vat_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
vat_numberYesSwiss VAT number, e.g. 'CHE-107.028.276 MWST'
include_detailsNoAlso fetch the holder's name/address/VAT dates (one extra request)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

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's added value is in naming the upstream authority (federal VAT register via UID register), disclosing the return shape, and warning that include_details costs one extra request. That extra-request note is genuine behavioral context an agent would not get 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence that front-loads the purpose, then formats, then return values, then use case — every clause carries information. The parenthetical format examples and details clause make it slightly heavy but nothing is redundant.

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?

There is no output schema, and the description compensates fully by enumerating the returns: valid true/false, the normalised VAT number, and holder name, address and VAT entry date when include_details is set. For a two-parameter read-only lookup, nothing an agent needs before calling is missing.

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%, so the baseline is 3. The description does add value by listing three accepted input formats ('CHE-107.028.276 MWST', 'CHE107028276TVA', '107028276'), implying normalization and tolerance of separators, and it restates the include_details side effect rather than just its boolean meaning.

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 whether a Swiss VAT number is valid and active in the federal VAT register via the UID register — and pins the domain to Swiss MWST/TVA/IVA numbers. An agent can distinguish this from generic company or municipality lookups 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 Guidelines4/5

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

Ends with an explicit use case, 'supplier/invoice checks', which gives the agent a concrete selection context. It stops short of naming an alternative tool or stating when not to use it, so it is clear guidance without exclusions.

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

Deploy Server

Other Tools