Skip to main content
Glama

Show VIES availability

vies_status
Read-onlyIdempotent

Shows which EU member state services in VIES are currently available. Use it when a check returned 'unavailable' to see whether the national service is down.

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

Input Schema

NameRequiredDescriptionDefault
country_codeNoOptional two-letter country code, e.g. DE. Greece is EL.
with_receiptNoOptional, default false. Set true only when the user asks for a signed receipt of this check for their files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / with_receipt
      Added value: +{
      +  "description": "Optional, default false. Set true only when the user asks for a signed receipt of this check for their files.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds the diagnostic framing (interpreting an 'unavailable' result) but says nothing about freshness, granularity, or coverage of the availability data returned. Adequate but thin beyond what annotations and the schema supply.

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?

Two short sentences, zero padding, with the purpose front-loaded and the usage trigger immediately following. Every clause carries information an agent needs.

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 simple two-optional-parameter read-only lookup with rich annotations and full schema coverage, the description supplies enough to call it correctly. It does not explain scope when country_code is omitted or the shape of the availability result, but no output schema exists, so that gap is minor.

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 country_code and with_receipt are already documented, including the Greece-is-EL caveat and the receipt opt-in. The description adds no parameter-level meaning beyond the schema, such as what happens when country_code is omitted and all countries are returned. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb and resource: it shows which EU member state VIES services are currently available. That is a clear diagnostic/reference function distinct from sibling validation tools like check_vat_id, though no sibling is named outright, so differentiation is inferential rather than explicit.

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?

It gives an explicit trigger condition: use it when a check returned 'unavailable' to determine whether the national service is down. There are no stated exclusions or named alternatives, but the when-to-use context is concrete and actionable for an agent handling a failed VAT check.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources