Skip to main content
Glama

MCP Europe Tools

by app.railway.up.mcp-europe-tools-production
OverviewDiscussionsAdmin

validate_tva_fr

Read-onlyIdempotent

Validates a French TVA intracom (VAT) number — the EU VAT identifier for French companies. Format is 'FR' + 2 alphanumeric key characters + 9-digit SIREN. Returns { valid: boolean, key: string, siren: string, tva: string }. When the key is numeric, validates using the official formula: key = (12 + 3 × (SIREN mod 97)) mod 97. Use when validating French supplier VAT numbers, processing cross-border EU invoices, or any intra-EU transaction requiring a verified French VAT identifier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tvaYesFrench TVA intracom number with or without spaces. Example: 'FR 40 303 265 045' or 'FR40303265045'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / tva / description
      Previous value: -"French TVA intracom number. Example: 'FR40303265045'"New value: +"French TVA intracom number with or without spaces. Example: 'FR 40 303 265 045' or 'FR40303265045'"
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "key": {
-      "type": "string"
-    },
-    "note": {
-      "type": "string"
-    },
-    "reason": {
-      "type": "string"
-    },
-    "siren": {
-      "type": "string"
-    },
-    "tva": {
-      "type": "string"
-    },
-    "valid": {
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "valid"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / tva / description
      Previous value: -"French TVA intracom number with or without spaces. Example: 'FR 40 303 265 045' or 'FR40303265045'"New value: +"French TVA intracom number. Example: 'FR40303265045'"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "key": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "siren": {
+      "type": "string"
+    },
+    "tva": {
+      "type": "string"
+    },
+    "valid": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "valid"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / tva / description
      Previous value: -"The French TVA number to validate. Spaces are automatically removed. Example: 'FR 40 303 265 045' or 'FR40303265045'"New value: +"French TVA intracom number with or without spaces. Example: 'FR 40 303 265 045' or 'FR40303265045'"
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses the return shape, the expected format, and the exact validation formula for numeric keys, which goes beyond the annotations' read-only/idempotent hints. This gives the agent insight into the tool's behavior and limitations.

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?

The description is three sentences, with no fluff. The first sentence states the action, second gives format and return, third gives formula and usage. Every sentence adds value and it is efficiently structured.

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?

For a simple read-only validation tool with one parameter, the description covers purpose, input format, output structure, validation logic, and use cases. There is no output schema, so the explicit return object description fills that gap completely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already covers the 'tva' parameter with a description and example, so baseline is 3. The tool description adds the structural rule 'FR' + 2 alphanumeric key + 9-digit SIREN, which enriches understanding beyond the schema's simple 'with or without spaces' note. This additional format detail raises the score.

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?

The description opens with 'Validates a French TVA intracom (VAT) number', which is a specific verb and resource. It clearly distinguishes from sibling validation tools by naming the French TVA and explaining it's for EU VAT identification, so the agent knows exactly its scope.

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

Usage Guidelines4/5

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

The description provides explicit usage context: 'Use when validating French supplier VAT numbers, processing cross-border EU invoices...'. This tells the agent when to select this tool, though it doesn't mention alternatives or exclusions, just the positive case.

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

All MCP Europe Tools 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