GadgetHumans API Hub

eu_vat

Validate an EU VAT number via VIES and return the registered company name, address and standard VAT rate.

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": {
      "vat": "<vat>"
    },
    "name": "eu_vat"
  }
}

Input Schema

Name	Required	Description	Default
`vat`	Yes	EU VAT number with country prefix, e.g. IE6388047V

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026
RemovedNov 6, 2026

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / vat

Added value: +{
+  "description": "EU VAT number with country prefix, e.g. IE6388047V",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "vat"
+]
```

AddedNov 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the external dependency (VIES) and the returned payload fields, but says nothing about VIES downtime, rate limits, or how an unregistered-but-well-formed number is reported.

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 with no filler; every clause (validation source, output fields) carries 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 lookup with no output schema, naming the source and the returned fields covers what an agent needs to invoke and interpret it. Only failure-mode behavior is left unaddressed.

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 country-prefix format with an example, so the description adds no parameter meaning beyond the schema. Baseline 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?

States a specific verb (validate), a specific resource (EU VAT number), the backing service (VIES), and what it returns. The 'EU' qualifier implicitly separates it from the sibling vat_validate, but the distinction is never made explicit.

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 tool name and 'EU' scope; there is no statement of when to pick this over the sibling vat_validate, nor any note about prerequisites or failure cases.

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

All GadgetHumans API Hub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.