Skip to main content
Glama

ReadingRate

Look up a list of books

lookup_books_batch
Read-onlyIdempotent

Matches a list of books to the ReadingRate catalog in one call, from ISBNs, titles, or titles with authors, and returns each match's ReadingRate analysis with a confidence level (exact, high, medium, low). Matching tolerates misspellings, such as titles read off book spines in a photo. A book the catalog does not hold is looked up in Open Library, a public book database, and comes back unmatched with what Open Library knows about it.

Use when the user gives several books at once, such as a photographed bookshelf or a pasted list, and wants them identified, ranked or compared. For a single book, use get_book_details.

Takes up to 20 books per call, more on some accounts; a longer list returns an error that gives the limit, so split it.

Example: {"books": [{"isbn": "9780140449136"}, {"title": "Crime and Punishment", "author": "Dostoevsky"}, {"title": "The Brothers Karamazov"}]}

Input Schema

NameRequiredDescriptionDefault
booksYesThe books to identify. Give each one an isbn, a title, or a title and author.

Output Schema

NameRequiredDescriptionDefault
matchedYesQueries matched to ReadingRate books
summaryYesCounts for the batch
unmatchedYesQueries with no catalog match

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly/openWorld/idempotent), the description discloses fuzzy-match tolerance for misspellings, the confidence-level taxonomy (exact/high/medium/low), the Open Library fallback for books not in the catalog with an 'unmatched' return shape, and the ~20-book cap with its error behavior. That is real behavioral context an agent cannot get from structured fields.

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?

Front-loaded with the core verb and return shape, then usage, then limits, then an example. Every paragraph serves a distinct purpose and none repeats the schema verbatim.

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

Completeness5/5

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

Output schema exists, so return values needn't be re-explained, yet the description still characterizes the result (analysis + confidence, or unmatched with Open Library data). Input forms, batch limits, and sibling routing are all covered for a one-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds value with a concrete JSON example showing all three item shapes and the batch size ceiling. It doesn't state whether isbn/title/author may be combined arbitrarily or which form matches best, so it stops short of a 5.

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?

States a specific verb and resource ('Matches a list of books to the ReadingRate catalog in one call') and enumerates the accepted input forms (ISBN, title, title+author) plus what each result contains (analysis + confidence level). It also distinguishes itself from the single-book sibling get_book_details by name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use conditions ('several books at once', 'photographed bookshelf or a pasted list') and names the alternative for the single-book case. It even pre-empts the failure mode by saying a longer list returns an error stating the limit and should be split.

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.