Skip to main content
Glama
RevClamp MCP Server

RevClamp MCP Server

revclamp_validate_eu_vat_vies

Normalizes EU B2B VAT IDs, including Greece to EL, and checks cross-border reverse-charge format eligibility locally or simulates VIES states for testing.

Instructions

Normalizes 27 EU member states + Northern Ireland (XI) B2B VAT IDs (auto-converting Greece GR -> EL) and checks cross-border reverse-charge format eligibility locally (or simulates VIES states when demo: true).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "revclamp_validate_eu_vat_vies"
  }
}

Input Schema

NameRequiredDescriptionDefault
demoNoRequired when using simulated viesMode values (VALID, INVALID, MS_UNAVAILABLE, GLOBAL_MAX_CONCURRENT_REQ) in local mode.
viesModeNoFORMAT_ONLY
buyerVatIdNo
supplyTypeNoCross-border transaction supply category: 'GOODS' (Directive 2006/112/EC Art. 138(1) intra-Community supply, default; permitted for Northern Ireland XI under Windsor Framework) or 'SERVICES' (Directive 2006/112/EC Art. 196 B2B reverse charge; excluded from EU VIES for Northern Ireland XI).GOODS
sellerCountryNoDE
consultationNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.20.29
  2. Removedv1.0.1
  3. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that validation is local by default and that demo simulates VIES states, plus the GR->EL normalization rule — useful behavioral facts. It does not state whether LIVE mode makes a network call, what happens when consultationNumber is supplied, or anything about return values or failure modes.

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?

A single dense sentence with the core operation and scope front-loaded and no filler. It is packed with parenthetical asides, which slightly hurts readability but every clause carries information.

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 6-parameter tool with no output schema and no annotations, the description covers the main operation and the demo switch but leaves half the parameters and the LIVE mode opaque. Adequate to start, but not sufficient for an agent to confidently invoke all parameter combinations.

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 only 33%, so the description should compensate more than it does. It adds meaning for demo and partially for viesMode, and the GR->EL conversion hints at buyerVatId handling, but sellerCountry, consultationNumber, and the LIVE enum value are underexplained in both the schema and the description.

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+resource: normalizes EU/XI B2B VAT IDs and checks cross-border reverse-charge format eligibility, with a note about simulation under demo. It is clearly distinct from all siblings (disputes, ROI, webhooks, reconciliation). It stops short of 5 because the relationship between 'checks locally' and the LIVE viesMode is left ambiguous.

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 context is implied (B2B reverse-charge eligibility checks) and the demo flag is explained, but there is no explicit guidance on when to choose this tool versus alternatives or when not to use it. Since no sibling performs VAT validation, the omission is less costly, but the agent still must infer the scenario.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.