Skip to main content
Glama

Check the IBAN mod-97 remainder

bpj_iban_mod97
Read-onlyIdempotent

Rearrange the IBAN and check its mod-97 remainder, covering syntax and checksum only.

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": {
      "value": "<value>"
    },
    "name": "bpj_iban_mod97"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. Beyond that the description only adds the scope limitation; it does not say whether an invalid IBAN yields a remainder value, a boolean, or an error, nor what normalization is applied before the mod-97 computation.

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?

A single tight sentence with the action and the scope limitation both up front and no filler. The wording is compact, though "rearrange the IBAN" is less immediately readable than plain "validate IBAN checksum".

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 no annotation about results, so the description should explain what the caller receives from the remainder check. It also leaves the input format requirements unstated, which matters for a validator whose output depends on exact string formatting.

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?

The single parameter has a generic schema title ("Input value") at 0% description coverage, so the description must carry meaning. Saying it operates on "the IBAN" does signal that the input is an IBAN string, but it never states accepted formatting (spaces, lowercase, country prefix) or the 240-character length intent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource: it checks an IBAN's mod-97 remainder. "Covering syntax and checksum only" scopes it away from registry/lookup validation, so an agent can distinguish it from siblings that verify existence rather than structure. Slightly held back by the jargon phrasing "rearrange the IBAN" and no explicit named alternative.

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?

The phrase "syntax and checksum only" implies what this tool does not do (no registry or reachability checks), which is useful implied guidance. There is no explicit when-to-use statement, no prerequisites, and no named alternative tool to route to for non-format validation.

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.