Skip to main content
Glama

Check tax ID format (about 50 countries)

validate_tax_id_format
Read-onlyIdempotent

Check the format of a business tax or registry ID offline: structure and, where the issuing authority publishes one, the check digit. Covers EU VAT numbers for all 27 member states (plus Spain NIF, France SIREN/SIRET, Finland Y-tunnus, Sweden organisationsnummer), United Kingdom VAT and company number, Switzerland UID, Norway, Iceland, Türkiye, United States EIN (structure only), Canada BN, Brazil CNPJ (including the alphanumeric format), Argentina, Chile RUT, Ecuador, Uruguay, Paraguay, Bolivia, Guatemala, Panama, Dominican Republic (RNC and cédula), Venezuela, Australia ABN/ACN, New Zealand NZBN/IRD, India GSTIN/PAN, Japan, South Korea, Taiwan, Singapore, Israel and South Africa. Returns the normalized ID, format and check-digit validity, verification_level "format", a review/fail assessment with reasons and, when one exists, the URL of the free official lookup. No registry is queried, so the result never confirms that the business exists or is active and never returns pass.

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": {
      "country": "<country>",
      "id": "<id>"
    },
    "name": "validate_tax_id_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ID as written, with or without the country prefix, spaces, dots or dashes, e.g. "DE 123 456 807" or "12.345.678/9013-11".
countryYesISO 3166-1 alpha-2 country code, e.g. "DE", "FR", "BR", "GB". "EL" is accepted for Greece and "UK" for the United Kingdom.
id_typeNoOptional ID type when the country has several, e.g. "vat", "siren", "siret", "nif", "crn", "abn", "acn", "gstin", "pan", "nzbn", "ird". Detected from the input when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"The ID as written, with or without the country prefix, spaces, dots or dashes, e.g. \"DE 136 695 976\" or \"33.000.167/0001-01\"."New value: +"The ID as written, with or without the country prefix, spaces, dots or dashes, e.g. \"DE 123 456 807\" or \"12.345.678/9013-11\"."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), it discloses the substantive behavioral limits: no registry is queried, results never confirm existence or activity, and it "never returns pass" — a critical nuance an agent cannot infer elsewhere. It also enumerates what the response contains, which matters 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.

Conciseness4/5

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

Purpose and the decisive caveat are front-loaded, and every sentence carries information. The long jurisdiction roster is dense and bloats a single sentence, but it earns its place by communicating coverage boundaries that the schema leaves open.

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 fully carries the return contract: normalized ID, format and check-digit validity, verification_level, review/fail assessment with reasons, and an official lookup URL when available. Combined with the explicit statement of what the result cannot prove, an agent has everything needed to call and interpret it correctly.

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 meaning to the country parameter by enumerating supported jurisdictions (all 27 EU states, UK, BR, IN, etc.), letting an agent judge coverage before calling. The conspicuous omissions — Colombia, Costa Rica, Mexico, Peru — also implicitly route to the corresponding siblings.

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 the format of a business tax or registry ID offline: structure and ... check digit") and explicitly bounds the operation as offline. The phrase "No registry is queried" cleanly separates it from an online counterpart such as validate_tax_id 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 Guidelines4/5

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

Gives clear context for use — offline structural/check-digit validation with verification_level "format" — and rules out a whole class of wrong expectations (existence, active status, pass results). It stops short of explicitly naming a sibling to use when registry confirmation is actually needed, so the alternative is implied rather than stated.

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