Skip to main content
Glama

Caelara Labs Compliance & Trust

vat_ein_checkdigit

Validate EU VAT number check digits and US EIN format

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": {
      "number": "<number>"
    },
    "name": "vat_ein_checkdigit"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesVAT number with country prefix, or US EIN (NN-NNNNNNN)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden; it does hint that the operation is a format/checksum validation rather than a live registration lookup, which is meaningful. However, it never states whether numbers are checked offline or against VIES, whether a VAT registration is confirmed as active, or what the response contains.

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?

A single, front-loaded sentence naming both supported input families with no filler. Nothing could be removed without losing information.

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?

For a one-parameter validator this is nearly sufficient, but with no output schema the description should state what a result looks like (boolean vs. structured per-country verdict) and clarify that check-digit validation is not a registration-status check. Those omissions are the main remaining gap.

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% and the single parameter already documents the accepted formats (country-prefixed VAT, NN-NNNNNNN EIN). The description adds no further detail such as accepted country prefixes or handling of spaces and separators, so it only matches, not exceeds, the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ("Validate") and two precise resources (EU VAT number check digits, US EIN format), so an agent knows exactly what the tool operates on. It does not explicitly distinguish itself from nearby validation siblings such as iban_bic_validator, though the resource names are distinctive enough to avoid confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to use this rather than a broader validation or lookup tool, and no mention of prerequisites, input source, or exclusions. The agent must infer the use case entirely from the resource names in the description.

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