Skip to main content
Glama

Book lookup by ISBN or by title and/or author: title

books
Read-only

Book lookup by ISBN (checked before the call) or by title and/or author: title, subtitle, authors, publishers, first publish year, median page count, ISBN-10 and ISBN-13 of the matching edition, languages, subjects, cover image URL, and the Open Library work and Wikidata ids. Data from Open Library (CC0). A title with no match is a 404, not charged. Up to 20 results. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "books"
  }
}

Input Schema

NameRequiredDescriptionDefault
isbnNoISBN-10 or ISBN-13 with or without hyphens (optional)
limitNoResults, 1 to 20, default 5
titleNoTitle words, up to 200 characters (optional)
authorNoAuthor name, up to 200 characters (optional)

Output Schema

NameRequiredDescriptionDefault
booksNo
countNo
queryNo
sourceNo
editionNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint the description discloses cost ($0.002 per successful call), the payment rail (x402, USDC on Base/Solana and 10 more networks), and that failed or 404 calls are not charged — exactly the billing and failure semantics an agent must know before spending. It also names the data source and license (Open Library, CC0), which the annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening purpose statement and the pricing/failure sentences are front-loaded and earn their place, but the long enumeration of return fields duplicates what the output schema already provides. The result is a dense block where roughly a third of the text is redundant with structured data.

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 four-parameter read lookup with a full output schema and annotations covering safety, the description supplies the missing pieces: matching modes, result cap, 404-on-no-match behavior, and billing. Only the relative precedence of ISBN vs. title/author when several are supplied is left unclear.

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 100%, so isbn, title, author and limit are already documented with types and the 1–20 bound. The description restates 'up to 20 results' and the ISBN/title/author split without adding format or matching-behavior detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first clause states a specific verb and resource plus both lookup modes ('by ISBN ... or by title and/or author'), and the field list makes the returned entity unambiguous. An agent can tell this is a bibliographic record lookup without opening the schema.

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?

It implies the two invocation paths (ISBN vs. title/author) and notes ISBN is 'checked before the call', which hints at precedence, but it never states when to prefer this over sibling lookups like wikidata or arxiv, nor when-not to use it. Usage is inferable but not explicitly guided.

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.

Resources