Skip to main content
Glama
Sign In

ENTIA Entity Verification

by io.github.entia-systems-core
OverviewDiscussionsAdmin

Verify VAT

verify_vat
Read-onlyIdempotent

FREE (no API key needed). Use when the user asks whether an EU VAT number is valid or active (live VIES check). Real-time EU VAT validation via VIES (27 countries). Returns {valid, name, address, vat_number, country, checked_at}. Some Member States (Spain among them) do not disclose name/address through VIES: name/address come back null with name_disclosure=withheld_by_member_state; use entity_lookup for the registered name.

Input Schema

NameRequiredDescriptionDefault
qNoEU VAT number (ESA28015865, A28015865, IE6388047V)
vatNoAlias for `q` — the VAT number.
queryNoAlias for `q`.

Output Schema

NameRequiredDescriptionDefault
_metaNo
queryNo
resultNoVIES answer: validity, registered name and address
vat_numberNo
country_codeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Real-time VIES validation.",
+  "properties": {
+    "_meta": {
+      "type": "object"
+    },
+    "country_code": {
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "result": {
+      "description": "VIES answer: validity, registered name and address",
+      "type": "object"
+    },
+    "vat_number": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Alias for `q`.",
+  "type": "string"
+}
    • addedInput schema / properties / vat
      Added value: +{
+  "description": "Alias for `q` — the VAT number.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "q"
-]New value: +[]
  3. Changed3 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / q / description
      Previous value: -"EU VAT number to validate against VIES. Accepts country prefix or bare number (e.g. ESA28015865, A28015865, IE6388047V)."New value: +"EU VAT number (ESA28015865, A28015865, IE6388047V)"
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover safety (readOnly, idempotent, openWorld), and the description adds meaningful context beyond them: free/no API key, live VIES reach, the exact return shape, and the important caveat that some Member States withhold name/address, yielding name_disclosure=withheld_by_member_state. That disclosure issue is exactly the kind of operational behavior an agent needs.

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?

Information is dense and front-loaded: pricing/auth, usage trigger, mechanism, return shape, and edge-case caveat in a few sentences. No sentence is filler, and the most decision-relevant facts come first.

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?

Even though an output schema exists, the description still prepares the agent for the response fields and the name-disclosure edge case. Combined with the annotations and schema, an agent has everything needed to call this correctly.

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 description coverage is 100%, so all three alias parameters (q, vat, query) are documented in the schema. The description says 'EU VAT number' but adds no format or alias guidance beyond the schema, so baseline 3 is appropriate.

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?

Names a specific verb and resource — real-time EU VAT validation via VIES across 27 countries — and explicitly distinguishes itself from entity_lookup for name resolution. An agent can identify the operation without opening the schema.

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?

States the triggering condition directly: 'Use when the user asks whether an EU VAT number is valid or active.' It also names the alternative, entity_lookup, for the registered-name case, so routing is unambiguous.

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

All ENTIA Entity Verification toolsInspect
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.

Resources