Skip to main content
Glama

Book ISBN metadata

bpj_book_isbn_metadata
Read-onlyIdempotent

Validate an ISBN-13 prefix and check digit and build Book metadata with author and language.

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": {
      "name": "<name>",
      "author": "<author>",
      "language": "<language>",
      "isbn": "<isbn>"
    },
    "name": "bpj_book_isbn_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
isbnYes
nameYes
authorYes
languageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: it performs ISBN-13 prefix and check-digit validation, implying failure modes for malformed ISBNs. It stops short of saying what happens on validation failure or what the built metadata contains.

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?

A single front-loaded sentence with no filler; validation is stated before construction, which matches the likely call order. Slightly terse given the number of undocumented parameters, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four required parameters, 0% schema coverage, and no output schema, the definition should explain what 'Book metadata' is returned and how each field is used. It omits the role of 'name' entirely and says nothing about the response or validation-error behavior, leaving meaningful gaps for a tool of this complexity.

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 0% and all four parameters are required, so the description is the only source of meaning. It clarifies that isbn is an ISBN-13 with a check digit and that author and language feed the metadata, but leaves the 'name' parameter unexplained and gives no format guidance (hyphens, digit-only, language tag syntax) despite 240-character limits on every field.

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?

The description names two specific operations (validate an ISBN-13 prefix and check digit; build Book metadata) on a clearly identified resource, which is far more informative than the title alone. It does not, however, contrast itself with related sibling tools such as bpj_bibtex_book_entry, so an agent must infer the distinction.

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 explicit when-to-use, when-not-to-use, or alternative guidance. The agent can infer that this is the tool for constructing a book record from ISBN plus author/language, but nothing states prerequisites or when another metadata tool would be preferable.

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.