Skip to main content
Glama

Qiniso

by io.github.qinisolabs

validate_vat

Read-only

USE THIS to verify an EU/EFTA VAT registration number's format and checksum before invoicing or onboarding a business — instead of trusting it looks right. Covers all EU members plus UK/EFTA. Pass the full number incl. country prefix (e.g. DE136695976) or the digits plus a country code. NOTE: checks format+checksum only; does NOT confirm the number is live-registered (that is a VIES lookup).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vatYesThe VAT number, ideally with its country prefix (e.g. DE136695976).
countryNoISO country code, if the number has no prefix (e.g. DE).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds that it checks format+checksum only, not live registration, which is useful context beyond the annotation. No contradiction.

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 sentences, well structured and front-loaded with action. Every sentence adds value with no redundancy or fluff.

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?

Given no output schema, the description adequately explains tool behavior (format+checksum check) and important limitation (not live registered). Among many sibling validation tools, it stands out with clear EU/EFTA scope.

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?

Schema covers both parameters with descriptions (100% coverage). Description adds practical context: full number with country prefix (e.g., DE136695976) or digits plus country code, which helps correct invocation.

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 clearly states the tool verifies EU/EFTA VAT registration number format and checksum, with a specific use case (before invoicing or onboarding). It distinguishes from VIES lookup, clarifying it does not confirm live registration.

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?

Explicitly says when to use ('before invoicing or onboarding') and when not to use (for live registration, use VIES lookup). Provides clear guidance on when this tool is appropriate versus alternatives.

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

All Qiniso toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a specific identifier or operation (e.g., validate_iban, parse_date, is_holiday). Even similar tools like validate_isbn and validate_isbn10 are distinct by version. There is no overlap or ambiguity.

Naming Consistency4/5

Most tools follow a verb_noun pattern (validate_xxx, parse_xxx, format_currency). The exception is 'next_holiday', which uses an adjective instead of a verb. Otherwise consistent.

Tool Count2/5

With 47 tools, the set is very large. While each tool is distinct, the count exceeds the recommended range (25+ is considered too many) and may overwhelm users or agents.

Completeness3/5

Covers a wide array of international identifiers and utilities, but notable gaps exist (e.g., no Canada SIN, India PAN, Mexico CURP). The set is broad but not exhaustive for the domain of data validation.

Resources