Skip to main content
Glama

Validate a business tax ID (any supported country)

validate_tax_id
Read-onlyIdempotent

Validate a business tax or registry ID for any supported country with the deepest check available for it. Norway (organisation number), Finland (Y-tunnus or VAT), France (SIREN, SIRET or VAT), Ireland (CRO company number) and Taiwan (unified business number) are checked live against the official open registry: legal name, status (active, dissolved, bankrupt, struck off and others), address, key dates, the source with its licence and the date of the data, verification_level "official_registry" and a pass/review/fail assessment with reasons. Ireland comes from the CRO daily snapshot, not a live query. Dominican Republic RNC (9 digits) is checked against our copy of the DGII RNC registry file, refreshed from the file the DGII publishes daily (legal and trade name, status, activity, payment regime); an 11-digit cédula of a natural person gets the format check only, without any name. Chile RUT is checked against our copy of the SII register of legal entities (nómina de personas jurídicas, refreshed a few times a year: see source.data_as_of): name, legal form, start date and término de giro (closure = fail). Canada BN (9 digits, or with a program account such as RT0001) is checked against our copy of the Corporations Canada federal corporations data, refreshed daily (Open Government Licence – Canada): name, status, registered office, dates; it covers federal corporations only, so a BN not found is review, never fail. For sole proprietorships (Norway ENK, French entrepreneurs individuels, Finnish sole traders) only the status is returned, without name or address. Peru, Mexico, Colombia and Costa Rica are answered by the same lookups as their own tools. Every other covered country (about 45, including EU VAT numbers, the United Kingdom, Brazil, Australia, India and Japan) gets the offline format check with verification_level "format", which 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ID as written, with or without the country prefix, spaces, dots or dashes, e.g. "974761076", "1003521-5", "FR90130004955", "98788", "03741302".
countryYesISO 3166-1 alpha-2 country code, e.g. "NO", "FI", "FR", "IE", "TW", "DO", "CL", "CA", "DE", "PE". "EL" is accepted for Greece and "UK" for the United Kingdom.
id_typeNoOptional ID type when the country has several, e.g. "siren", "siret", "vat", "ytunnus", "cro", "orgnr", "ubn", "rnc", "cedula", "rut", "bn". 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. \"923609016\", \"0112038-9\", \"FR27552120222\", \"249885\", \"22099131\"."New value: +"The ID as written, with or without the country prefix, spaces, dots or dashes, e.g. \"974761076\", \"1003521-5\", \"FR90130004955\", \"98788\", \"03741302\"."
  2. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO 3166-1 alpha-2 country code, e.g. \"NO\", \"FI\", \"FR\", \"IE\", \"TW\", \"DE\", \"PE\". \"EL\" is accepted for Greece and \"UK\" for the United Kingdom."New value: +"ISO 3166-1 alpha-2 country code, e.g. \"NO\", \"FI\", \"FR\", \"IE\", \"TW\", \"DO\", \"CL\", \"CA\", \"DE\", \"PE\". \"EL\" is accepted for Greece and \"UK\" for the United Kingdom."
    • changedInput schema / properties / id_type / description
      Previous value: -"Optional ID type when the country has several, e.g. \"siren\", \"siret\", \"vat\", \"ytunnus\", \"cro\", \"orgnr\", \"ubn\". Detected from the input when omitted."New value: +"Optional ID type when the country has several, e.g. \"siren\", \"siret\", \"vat\", \"ytunnus\", \"cro\", \"orgnr\", \"ubn\", \"rnc\", \"cedula\", \"rut\", \"bn\". Detected from the input when omitted."
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, openWorld, non-destructive), yet the description adds substantial behavior beyond them: verification_level values ('official_registry' vs 'format'), pass/review/fail assessment with reasons, Ireland sourced from a daily snapshot rather than a live query, Canada non-found treated as review 'never fail', and sole proprietorships returning status only without name or address. It also discloses data freshness ('refreshed a few times a year: see source.data_as_of'), which no annotation conveys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is front-loaded with the core statement, but the body is one very long block of semicolon-and-parenthesis-chained country notes that is hard to scan. Nearly every clause carries real information, but the lack of structure (no list or paragraph breaks) costs readability without the content being wasteful.

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 returned fields (legal name, status, address, key dates, source with licence, data date, verification_level, pass/review/fail reasons) and their per-country limitations. For a tool with this many country branches, an agent has everything needed to interpret results 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; the description earns above that by adding meaning about ID shapes and country semantics (Dominican RNC 9 digits vs 11-digit cédula getting format-only with no name, Canada BN 9 digits or with a program account such as RT0001, Chile RUT closure implying fail). Only id_type is left entirely to 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?

The first sentence states a specific verb and resource ('Validate a business tax or registry ID') plus the operative distinction from its sibling: 'the deepest check available for it', as opposed to a format-only check. The country-by-country enumeration makes it unmistakable which lookups this tool performs versus the country-specific sibling tools it says are 'answered by the same lookups'.

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?

The description gives clear conditions for what happens per country and explicitly says Peru, Mexico, Colombia and Costa Rica delegate to the same lookups as their own tools, which is real routing guidance. It does not explicitly say when to prefer validate_tax_id_format over this tool, so the alternative is only implied via the 'offline format check' paragraph.

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