Skip to main content
Glama

Verify an LEI checksum

bpj_lei_checksum
Read-onlyIdempotent

Verify the character format and MOD 97-10 checksum of a 20-character legal entity 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_lei_checksum"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds that two distinct validations occur (format plus MOD 97-10), which implies two distinct failure modes. However, it says nothing about the return value or how format failure differs from checksum failure, and no output schema exists to fill that gap.

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 front-loaded sentence with no filler; the verb, the two checks, and the input domain all appear before any trailing detail. Nothing redundant or padded.

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 validator with no output schema, the agent still needs to know what a success or failure result looks like and whether the input is normalized before checking. The description covers the input domain but not the result shape, leaving a real gap for an agent that must interpret the response.

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 0% and the schema only says 'string, maxLength 240', which is far looser than the real constraint. The description supplies the meaningful constraint that the value is a 20-character LEI, which adds real semantics beyond the structured field. It omits case/whitespace normalization rules, which is the remaining gap.

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?

States a specific verb ('Verify') and a specific resource with two named sub-checks (character format and MOD 97-10 checksum) on a 20-character legal entity identifier. This clearly separates it from the ISIN and NMEA checksum siblings by naming the identifier type. It stops short of an explicit 'not for X' differentiation, so a 4 rather than 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 statement of when to use this versus the sibling checksum tools, nor any precondition such as whether input must already be uppercase or stripped of separators. The only implied guidance is that the value is expected to be a 20-character LEI, which an agent could infer from the purpose alone.

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.