Skip to main content
Glama

Check VAT service availability

check_vies_availability
Read-onlyIdempotent

Use this when the user asks for a vies check, vat number validation, or bulk vat number check after unavailable answers and needs member-state service status. Reads VIES status for 28 country services, cached for 120 seconds. Do not use for validating an individual VAT number.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sourceYes
availableYes
countriesYes
retrievedUtcYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, so the safety profile is covered. The description still adds real context beyond them: the 28-country scope and a 120-second cache, both of which affect how an agent should interpret freshness and coverage.

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?

Three sentences, each doing work: usage trigger, behavior/scope, and exclusion. It is front-loaded well, though the first sentence is slightly clunky with its stacked trigger phrases, costing it the top mark.

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 zero-parameter status tool with full annotations and an output schema, this is complete: the agent knows the scope, cache freshness, and when to route to the sibling instead. Nothing needed to call it correctly is missing.

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 there is nothing parameter-specific to explain and the baseline is 4. The description correctly implies no per-request input by describing a global status read rather than a per-VAT lookup.

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 states a specific verb and resource — reading VIES service status for 28 country services — and explicitly rules out individual VAT validation, which cleanly separates it from the sibling check_vat_numbers. An agent can tell exactly what this tool does 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?

It gives an explicit trigger (user asks for a VIES/VAT check, especially after unavailable answers and needs member-state service status) and an explicit exclusion (do not use for validating an individual VAT number). That is the full when/when-not/alternative pattern in miniature.

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