Skip to main content
Glama

Upgrade ISBN-10 to ISBN-13

bpj_isbn10_upgrade
Read-onlyIdempotent

Validate an ISBN-10 including X check digits, add the 978 prefix and calculate its new ISBN-13 digit.

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": {
      "isbn": "<isbn>"
    },
    "name": "bpj_isbn10_upgrade"
  }
}

Input Schema

NameRequiredDescriptionDefault
isbnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 closed-world scope, so the safety profile is covered. The description usefully adds that check-digit validation occurs before conversion and that the 'X' check character is accepted. It does not say what happens on an invalid ISBN-10 (error vs. returned failure) or what the response looks like, which matters for a no-output-schema tool.

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 short sentence, front-loaded with the validation step followed by the two conversion steps in execution order. Nothing is 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 simple one-parameter tool with annotations and no output schema, the description should state the return value (presumably the 13-digit ISBN-13 string) and error behavior on an invalid input. Those gaps are the main incompleteness, though the core transformation is fully described.

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%, so the description must carry the parameter meaning. It tells the agent the input is a validated ISBN-10 that may contain an X check digit, which is real value beyond the bare 'ISBN-10' title. However, with maxLength 32 it is unclear whether hyphens or spaces are accepted in the input, and the description does not address that.

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 and resource chain: validate an ISBN-10, add the 978 prefix, compute the ISBN-13 check digit. The agent can tell exactly what transformation the tool performs. It stops short of naming the nearest sibling (bpj_book_isbn_metadata), so the ISBN-10 vs ISBN-metadata distinction must be inferred from names rather than stated.

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 implied by the described transformation: call it when you have an ISBN-10 and need the ISBN-13 form. There is no explicit when-not guidance, no mention of what to do with an already-13-digit ISBN, and no alternative tool named.

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.