Skip to main content
Glama

UID prüfen

validate_uid
Read-onlyIdempotent

Check an EU VAT number (UID) against VIES, the EU register. Returns the status and, where the member state publishes it, the registered name and address. Use it when the user gives a UID or asks whether one is valid. Read-only; update_client and update_profile run the same check before saving.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uid": "<uid>"
    },
    "name": "validate_uid"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYese.g. ATU12345678 or DE123456789

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered; the description adds value by naming the external dependency (VIES) and describing the partial return payload, which matters because there is no output schema. It does not cover failure modes such as malformed UID format or VIES being unavailable, which is the main remaining gap for an open-world tool.

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?

Three short sentences: what it does and returns, when to use it, and the read-only/redundancy note. Front-loaded and every sentence carries distinct information with no repetition of the schema.

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, the description correctly compensates by describing the return shape, and it states the external register and read-only nature. What is missing is behavior on invalid input or an unavailable VIES endpoint, which would matter for a single-shot external validation call.

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?

Only one parameter and schema coverage is 100%, with example formats (ATU12345678, DE123456789) already in the schema. The description adds only the semantic gloss that the string is an EU VAT number, so baseline 3 applies.

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?

States a specific verb and resource ("Check an EU VAT number (UID) against VIES") and names the authoritative register, which immediately distinguishes it from the client/invoice CRUD siblings. It also states what comes back (status plus registered name/address where published).

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?

Explicit trigger condition: "Use it when the user gives a UID or asks whether one is valid." It additionally tells the agent that update_client and update_profile already run the same check before saving, which prevents a redundant call — a genuinely useful routing hint.

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