Skip to main content
Glama

isbn_validate

Validate ISBN-10 or ISBN-13 check digits and convert between forms, returning valid flags, corrected values, and GTIN-14 data to ensure accurate book identifiers.

Instructions

ISBN-10 / ISBN-13 validation and conversion (ISO 2108 check digits): valid flag, expected check digit, corrected value, both forms, GTIN-14, registration group hint. Costs 0.001 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": "isbn_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
isbnYesISBN-10 or ISBN-13

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well, disclosing the per-call price (0.001 USDC on Base via x402) and the precise failure mode when unauthenticated (a 402 challenge rather than an error or empty result). It also enumerates what comes back, but does not clarify whether an invalid ISBN still incurs the charge or whether the charge applies only to valid results despite the phrase 'per successful call'.

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?

Two sentences, front-loaded with the operation and standard, then the cost and auth behavior. The dense output-field list is compact and every clause carries information; nothing is padding.

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?

There is no output schema, and the description compensates well by naming the returned fields (valid flag, expected check digit, corrected value, both forms, GTIN-14, group hint). The remaining ambiguity is the billing boundary between a failing validation and a successful call, which matters for a paid tool.

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 description coverage is 100% and the single parameter is already documented as 'ISBN-10 or ISBN-13', which is essentially what the description repeats. The mention of a 'corrected value' hints that malformed hyphenation or spacing is tolerated, but no accepted input formats are spelled out, so the baseline 3 applies.

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?

It gives a specific verb pair (validate and convert) plus the exact resource (ISBN-10 / ISBN-13) and cites the governing standard, ISO 2108, so an agent knows precisely what it does. It stops short of differentiating itself from the sibling gtin_validate, even though it mentions emitting a GTIN-14 form, leaving the overlap for the agent to infer.

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 context is implied by the resource itself (checking or correcting a book identifier), and the payment precondition is stated explicitly: a payment key is required or the call returns a 402 challenge. There is no when-to-use-versus-alternative guidance, such as when to prefer this over gtin_validate for a 13/14-digit code.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.