Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_compliance_vat_ein_checkdigit

Validate EU VAT number check digits and US EIN formats to catch invalid tax IDs before compliance checks.

Instructions

[Compliance & Trust] Validate EU VAT number check digits and US EIN format Measured p50 12 ms, p95 16 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://compliance.caelaralabs.com.

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": "caelara_compliance_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 observedv1.0.1

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 burden. It does add genuine behavioral context that structured fields do not: measured latency (p50 12 ms, p95 16 ms) with a dated benchmark source and the upstream host. However, it never states what a validation response contains (valid flag, normalization, country inference), whether the call is side-effect free, or what errors look like — significant gaps for a validator with 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?

Three short, front-loaded sentences with the purpose first and no redundancy. The benchmark date/site and endpoint URL are useful but read as boilerplate appended to every tool in this family, costing a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-style validator with no annotations and no output schema, the definition should say what the result looks like and what happens on malformed input. Latency and host are covered, but return semantics are entirely absent, leaving a meaningful hole.

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's description already specifies both accepted formats (country-prefixed VAT or NN-NNNNNNN EIN). The prose adds nothing beyond that, so the baseline of 3 applies.

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?

Specific verb plus concrete resources: 'Validate EU VAT number check digits and US EIN format.' The scope is unambiguous, and the VAT check-digit framing distinguishes it in spirit from the sibling rate-lookup tool. It stops short of naming or contrasting any sibling explicitly, which keeps it at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is only implied by the validation scope — an agent can infer this is the tool for checking a VAT/EIN string, but there is no statement of when to prefer it over siblings (e.g., the IBAN/BIC validator or geo VAT rate lookup), no prerequisites, and no 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