Skip to main content
Glama

MaxRechnung

IBAN prüfen + Bankname

check_iban
Read-only

Tarif: in jedem Tarif (Free, Pro, Business).

IBAN prüfen + Bankname

Zustandslos. Scope checks:read. Prüft Zeichen und Länge nach ISO 13616 (keine Mod-97-Prüfsumme) und liefert für gültige deutsche IBANs den Banknamen aus der vierteljährlichen Bundesbank-BLZ-Datei sowie die achtstellige blz. Für Nicht-DE-IBANs bleiben bank_name leer und blz null.

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

Input Schema

NameRequiredDescriptionDefault
ibanNoQuery-Parameter iban

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the readOnly/non-destructive annotations: declares statelessness, the required API scope, the exact validation depth (characters and length per ISO 13616, explicitly NOT the mod-97 checksum), and the DE vs non-DE output behavior (`bank_name` empty, `blz` null). What remains unstated is what is returned for a failing IBAN.

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?

Compact and mostly front-loaded: plan availability, then purpose, then behavior. The title restatement ('IBAN prüfen + Bankname') duplicates the title field and is the one sentence that does not fully earn its place.

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 carries the return-value burden and does so for `bank_name` and `blz`, including the quarterly Bundesbank BLZ source. The gap is the lack of any indication of the validity result itself for a failing IBAN.

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 coverage is 100%, though the schema text is bare ('Query-Parameter iban'). The description does not explain the `iban` parameter's accepted format directly, but the ISO 13616 character/length note gives indirect guidance. Baseline 3 applies when the schema already covers the parameter.

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 concrete verb and resource ('IBAN prüfen') plus the value-add ('+ Bankname'), and scopes it to character/length validation per ISO 13616. An agent can tell this apart from the VAT-Check siblings 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives useful context — available in every plan, stateless, requires scope `checks:read` — but never states when to prefer this over alternatives (e.g. the VAT-id checks) or when it is unnecessary. Usage is implied by the purpose rather than guided explicitly.

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