Skip to main content
Glama
Sign In

mcp-server

by com.interzoid
OverviewDiscussionsAdmin

interzoid_eu_vat_rates

Read-onlyIdempotent

Current VAT rates for any European country (EU-27, EEA, UK, Switzerland, and non-EU Europe): standard, reduced, super-reduced, zero-rated, and exempt categories, plus registration thresholds and territorial exceptions. For cross-border e-commerce, invoicing, and VAT compliance. Cost: $0.25 USDC via x402.

Input Schema

NameRequiredDescriptionDefault
lookupYesCountry name, ISO code, city, or address
languageNoOptional. Two-letter code for results in that language (default English): fr, de, it, es, ja, pt, zh, ar, nl, el, tr, ko, sv, vi, th, id. Same price in every language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
+  "description": "Optional. Two-letter code for results in that language (default English): fr, de, it, es, ja, pt, zh, ar, nl, el, tr, ko, sv, vi, th, id. Same price in every language.",
+  "enum": [
+    "fr",
+    "de",
+    "it",
+    "es",
+    "ja",
+    "pt",
+    "zh",
+    "ar",
+    "nl",
+    "el",
+    "tr",
+    "ko",
+    "sv",
+    "vi",
+    "th",
+    "id"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / lookup / examples
      Added value: +[
+  "Germany"
+]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, open-world, idempotent, non-destructive behavior. The description adds valuable behavioral context beyond annotations: the exact payment cost ($0.25 USDC via x402) and the breadth of returned data including registration thresholds and territorial exceptions.

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 efficient sentences, front-loaded with the core scope and content. Every sentence earns its place, including the cost note, with no filler.

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?

Given full schema coverage and annotations, the description adds the key missing contextual pieces: geographic coverage, rate categories, registration thresholds, territorial exceptions, and cost. It does not describe the exact response shape, but the listed content categories give an agent sufficient confidence to call the tool.

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 both parameters are fully documented in the schema. The description adds no additional meaning about the 'lookup' field (e.g., that city/address input resolves to a country) or the 'language' option. Baseline 3 is appropriate.

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 clearly states the resource (current VAT rates) and its exact geographic scope (EU-27, EEA, UK, Switzerland, non-EU Europe), plus the rate categories returned. It does not explicitly distinguish itself from siblings like interzoid_sales_use_tax_rates or interzoid_customs_duty_rates, which is the only gap for a 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?

It names relevant use cases ('cross-border e-commerce, invoicing, and VAT compliance'), giving implied usage context. However, it does not state when to prefer this over sibling tools such as sales/use tax or customs duty lookups, nor does it provide explicit exclusions.

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

All mcp-server 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