Skip to main content
Glama

Check an ISIN checksum

bpj_isin_checksum
Read-onlyIdempotent

Expand letters and verify the Luhn checksum in a 12-character securities identifier.

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

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/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. The description adds the actual algorithm (letter expansion then Luhn) which is genuinely useful, but it says nothing about the return value (boolean vs. error vs. corrected digit) or how malformed input is handled.

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?

A single tightly-written sentence with the algorithm and the input domain front-loaded and no filler whatsoever.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter checksum utility this covers the core operation, but with no output schema the description should say what a pass/fail looks like and what happens on invalid length or non-alphanumeric input. Those omissions are the main reason an agent could still call it correctly but misinterpret the result.

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 0% for the single 'value' parameter, so the description carries the burden and does partially meet it by saying the input is a 12-character securities identifier. It leaves a gap: the schema permits up to 240 characters, which the description neither explains nor reconciles, and it says nothing about formatting (whitespace, case).

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 gives a specific verb chain ('expand letters and verify the Luhn checksum') against a specific resource ('12-character securities identifier'), which pins down ISIN validation rather than LEI, CUSIP, or IMEI. It does not explicitly name a sibling to contrast with, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of what to do when the input fails the check. The agent must infer that this is the right tool purely from the tool name and the phrase 'securities identifier'.

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.