Skip to main content
Glama

Cash-service.pl

Weryfikator numeru konta (NRB/IBAN PL)

numer_konta
Read-onlyIdempotent

Sprawdza poprawność polskiego numeru rachunku bankowego (26 cyfr, suma kontrolna mod 97) i rozpoznaje bank po numerze rozliczeniowym. Używaj, gdy ktoś podaje numer konta i pyta, czy jest poprawny albo z jakiego banku.

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": {
      "numer": "<numer>"
    },
    "name": "numer_konta"
  }
}

Input Schema

NameRequiredDescriptionDefault
numerYesNumer rachunku: 26 cyfr, dopuszczalne spacje i prefiks PL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that by disclosing the validation mechanism (mod 97 checksum over 26 digits) and that a bank identifier is derived from the routing portion. It does not say what happens for an invalid number (error vs. a negative result), which is the main remaining ambiguity for a validator with no output schema.

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: capability first, invocation condition second. Every clause carries information — the digit count, the checksum, the bank recognition, and the trigger — with no filler or repetition of the title.

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 single-parameter, read-only, closed-world validator with full schema coverage and strong annotations, the description covers what the tool does and when to call it. The only shortfall is the absent return contract (what an invalid number yields), which matters somewhat because there is no output schema, but it is a narrow gap for a tool this simple.

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 description coverage is 100% and the single parameter already documents the 26-digit format plus tolerance for spaces and a PL prefix. The description restates the 26-digit and checksum facts but adds no new syntax, normalization, or edge-case guidance (e.g. whether hyphens or lowercase 'pl' are accepted). Baseline 3 is appropriate when the schema carries the parameter semantics.

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 names a specific verb and resource ('Sprawdza poprawność polskiego numeru rachunku bankowego') and adds a second concrete capability ('rozpoznaje bank po numerze rozliczeniowym'). It also pins the domain precisely (26 cyfr, suma kontrolna mod 97), which no sibling tool covers, so an agent can distinguish it immediately.

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?

It states an explicit trigger: use it when someone supplies an account number and asks whether it is valid or which bank it belongs to. That covers the two realistic invocation intents. It does not name exclusions or alternative tools, but no sibling plausibly overlaps here, so the guidance is clear without being exhaustive.

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