Skip to main content
Glama

MaxRechnung

USt-IdNr. prüfen (VIES oder qualifiziert per BZSt)

check_vat_id
Read-only

Tarif: ab Business (darunter antwortet die API mit plan_required).

USt-IdNr. prüfen (VIES oder qualifiziert per BZSt)

Zustandslos — speichert nichts. Scope checks:read.

Ohne weitere Parameter: EU-weite VIES-Abfrage — method: "vies", status valid / invalid / not_eu / unavailable (reason nennt den Grund).

Mit requester_vat_id = deutscher USt-IdNr. plus name und city: qualifizierte BZSt-Bestätigung (§ 18e UStG) — method: "bzst", status valid / invalid / not_eligible (Problem mit der Absender-USt-IdNr.) / unavailable; bei valid liefert matches die Abgleichcodes A/B/C/D für Firmenname / Straße / PLZ / Ort.

Um das Ergebnis an einer Rechnung / einem Kunden festzuhalten: POST /invoices/{id}/vat-check bzw. POST /customers/{id}/vat-check.

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_vat_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOrt (BZSt qualifiziert).
nameNoFirmenname (BZSt qualifiziert).
streetNoQuery-Parameter street
vat_idNoQuery-Parameter vat_id
postcodeNoQuery-Parameter postcode
requester_vat_idNoDeutsche USt-IdNr. des Anfragenden. Ist sie gesetzt und deutsch, fragt die API das BZSt statt VIES, auch ohne Firmendaten (dann einfache Bestätigung).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint/destructiveHint it discloses that the call is stateless (saves nothing), the required scope checks:read, and the plan gate (Business or higher, otherwise plan_required). It also documents the failure modes per mode (not_eu, not_eligible, unavailable) and what reason and matches contain.

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?

Well front-loaded: plan gate, purpose, scope, then the two modes, then the persist alternative. The only waste is repeating the title verbatim as the second line, which adds no information.

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?

There is no output schema, and the description compensates fully by enumerating the possible status values per mode, the reason field, and the matches structure. Combined with the stateless/scope/plan disclosures, an agent has everything needed to call this correctly.

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 coverage is 100%, so baseline is 3, but the description adds real meaning the schema placeholders lack: requester_vat_id must be a German VAT ID and drives mode selection, while name/city are the qualified BZSt inputs and street/postcode feed the A/B/C/D match codes. Only the exact role of vat_id itself (the subject being checked) is left implicit.

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+resource (USt-IdNr. prüfen) and immediately splits it into two concrete modes: plain EU-wide VIES lookup vs. qualified BZSt confirmation. It also marks the boundary to the persisting variants (POST /invoices/{id}/vat-check, POST /customers/{id}/vat-check), so an agent can tell the stateless check apart from the persist-to-entity siblings.

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?

Gives an explicit condition-to-mode mapping: no extra parameters = VIES; requester_vat_id as a German VAT ID plus name and city = qualified BZSt. It even clarifies that a German requester_vat_id alone switches to BZSt with a simple confirmation, and it names the alternative endpoints to use when the result must be attached to an invoice or customer.

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