Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

IBAN validation: validate an IBAN

validate_iban
Read-only

Check an IBAN's format, its country-specific length and its mod-97 check digits, and return it formatted in groups of four. Use before saving bank details or paying out. Example: iban=SE45 5000 0000 0583 9825 7466. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "iban": "<iban>"
    },
    "name": "validate_iban"
  }
}

Input Schema

NameRequiredDescriptionDefault
ibanYesThe IBAN, spaces allowed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/destructive/idempotent, so the description's restatement that it 'reads or computes only and changes nothing' is redundant, but it adds genuinely new behavior: per-call pricing ($0.01, first 25 free), failed calls free, and the consequence that repeats are billed. The only missing piece is what an invalid IBAN returns (error vs. structured failure), which matters for a validation tool.

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?

Front-loaded with the function, then usage, then example, then cost — a sensible ordering with little waste. The pricing clause is dense but each element (price, free tier, failed-call policy, billing on repeat) earns its place for a paid endpoint.

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?

For a one-parameter tool with no output schema, the description covers input format, the checks performed, the returned formatting, and the billing model. The gap is the failure path — an agent cannot tell whether an invalid IBAN raises an error or returns a validity flag — which is the one thing still needed before calling.

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% and the single parameter already documents 'spaces allowed,' so the schema carries the load. The description's worked example (iban=SE45 5000 0000 0583 9825 7466) still adds value by showing the accepted spaced format concretely, though nothing is said about country prefixes or normalization edge cases.

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?

Names a specific verb and resource and enumerates exactly what is checked: format, country-specific length, mod-97 check digits, plus a normalization output (groups of four). An agent can distinguish this from bic_validate or validate_luhn without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly says 'Use before saving bank details or paying out,' which gives a concrete decision point for invoking it. It stops short of naming when not to use it or pointing to the related sibling (e.g., BIC validation), so it is clear context without exclusions.

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.