Skip to main content
Glama

Validate tax ID format worldwide

validate_tax_id_format
Read-onlyIdempotent

Offline check of format and check digit for up to 50 tax or company numbers outside the EU (e.g. GB VAT, NO, AU ABN, NZ IRD, SG UEN, JP corporate number, CA BN, US EIN, IN GSTIN, BR CNPJ, MX RFC, TR, ZA, KR, AR, CL, CN, CO, IL, RU, UA) as well as EU VAT IDs and Swiss UIDs. Each answer states its depth: 'only the format was checked' or 'not supported'. It never says that a number is registered.

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

Input Schema

NameRequiredDescriptionDefault
tax_idsYes1 to 50 numbers, each with its country.
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. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / tax_ids / items / additionalProperties
      Added value: +false
    • removedInput schema / properties / tax_ids / items / properties / number / 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.8/5.0
Behavior5/5

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

Beyond the standard annotations (safe/read-only), the description provides vital behavioral details. It clarifies the check is 'offline,' defines the granularity of the output ('only the format was checked' or 'not supported'), and sets the constraint that it cannot validate registration status.

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?

The description is highly dense, listing dozens of examples to define its scope, which makes it long. However, every piece of information is necessary and strategically placed to define the tool's boundaries and capabilities efficiently.

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?

Given that there is no output schema, the description is exceptionally complete regarding expected outcomes. It clearly states that the response depth will be restricted to whether the format was checked or not supported, preventing incorrect agent interpretation of the results.

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?

While the schema is 100% covered, the description adds critical semantic meaning. It clarifies that the primary parameter `tax_ids` expects a structured array of `country` codes and `number` strings, which helps the agent understand the necessary input structure for diverse international IDs.

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 purpose is extremely specific: performing an offline check of both format and check digits. It clearly distinguishes its function by defining a vast, specific scope, naming both international (e.g., JP corporate number) and regional (e.g., EU VAT, US EIN) IDs.

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?

The definition provides excellent usage guidance by explicitly stating its applicability (international/EU) and, critically, its limitations. It warns the agent that the results are only about format/check digits and explicitly 'never says that a number is registered.'

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