Skip to main content
Glama
Sign In
VIES VAT Validator MCP

VIES VAT Validator MCP

by PanStories
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_supported_countries

Retrieve the countries supported by VIES for VAT validation, including country code, native name, and local VAT term.

Instructions

返回支持 VAT 校验的国家列表：代码 + 母语名 + 当地 VAT 叫法（如 USt-IdNr. / Partita IVA / btw-nummer）+ 中英名。List VIES-supported countries with native name and local VAT term.

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": "list_supported_countries"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose the shape of what comes back (country code plus three naming variants). It does not say whether the list is static, cached, or sourced live from VIES, which is the one behavioral fact that would matter for a reference-data tool.

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?

Two short sentences with the resource front-loaded and concrete examples (USt-IdNr., Partita IVA, btw-nummer) that make the output tangible. The English sentence is largely a restatement of the Chinese one, which is mild redundancy but appropriate for a bilingual audience.

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?

With no output schema, annotations, or parameters, the description is the sole carrier of information, and it does describe the returned fields. Nothing an agent needs in order to invoke this trivial zero-arg tool is missing, though origin/freshness of the list is unstated.

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 tool takes zero parameters, so the baseline of 4 applies. There is nothing for the description to clarify beyond the empty schema.

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 states a specific verb and resource ('return the list of countries that support VAT validation') and enumerates the returned fields (code, native name, local VAT term, Chinese/English names). It does not explicitly distinguish itself from siblings like validate_vat, but the noun phrase 'list of countries' makes the scope unmistakable.

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: an agent would infer this is a reference lookup to run before or alongside validate_vat/check_vat_format. There is no explicit when-to-use statement, no mention of the sibling tools, and no guidance on whether this list should gate validation calls.

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

Deploy Server

Other Tools