Skip to main content
Glama

Calculate a CUSIP check digit

bpj_cusip_check_digit
Read-onlyIdempotent

Derive the alternating-weight check digit from an eight-character CUSIP body.

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

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 the algorithm class (alternating weight), but says nothing about the return shape or what happens with a malformed or non-eight-character input.

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?

One front-loaded sentence with no waste; the operative constraint (eight-character body) arrives immediately.

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 pure single-parameter calculation with a strong annotation set and no output schema, the definition covers the essentials. Only the returned check digit's format and invalid-input behavior are left unstated.

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 property is only titled 'Input value' with maxLength 240, so the description carries the burden. It usefully clarifies that the parameter is the eight-character CUSIP body, but leaves the permitted character set and the length-vs-240 discrepancy unexplained.

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?

Specific verb plus resource: 'Derive the alternating-weight check digit' from a 'CUSIP body'. The domain term CUSIP clearly separates it from the IMEI/ISSN check-digit siblings, though the description never states the distinction explicitly.

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?

Usage is only implied by the domain terminology; there is no explicit when-to-use, when-not-to-use, or prerequisite (e.g. that the input must be the eight-character body without the existing check digit). Enough for a narrowly scoped utility, but no routing guidance.

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.