Skip to main content
Glama

Calculate an ISSN check digit

bpj_issn_check_digit
Read-onlyIdempotent

Calculate the modulo-11 check character for a seven-digit serial 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_issn_check_digit"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 usefully discloses the algorithm class (modulo-11) but says nothing about invalid-input behavior, whether hyphens or an existing check character are tolerated, or whether the result may be 'X'.

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?

One short, front-loaded sentence with no filler. It is efficient, though its terseness is part of why behavioral and parameter gaps remain.

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?

This is a simple pure function with full annotation coverage and no output schema, so the bar is modest. Still, for an agent to call it correctly it should know the expected input shape (7 digits, no check char) and the return form (single character, possibly 'X'), neither of which is stated.

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% and the single parameter is just 'value', so the description must carry the meaning. It partially does by specifying a seven-digit serial identifier (i.e., the payload without the check character), but leaves open formatting questions such as hyphens, whitespace, and the 240-character maxLength.

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 (Calculate) and resource (modulo-11 check character for a seven-digit serial identifier), so the operation is unambiguous. It never names ISSN in the body, relying on the name/title, and it does not distinguish itself from near-identical siblings like bpj_cusip_check_digit or bpj_imei_check_digit, which is why it stops short of 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 guidance on when to use this versus the other check-digit siblings, nor any exclusion such as 'input must not already contain the check character'. The agent must infer the call context entirely from the name.

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.