Skip to main content
Glama

Get similar books

get_similar_books
Read-onlyIdempotent

List the books in the ShelfClub catalog whose mood, vibe, pace and genre tags overlap most with those of a given book, chosen from its 10,000 most-read books. The tags are machine-generated, or voted for by at least three readers of the book, and a book that has none has no similar books. Returns up to 10 books, each with its ShelfClub id, authors, description, reader rating, series, tags and shelfclub.app link.

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": {
      "id": "<id>"
    },
    "name": "get_similar_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ShelfClub id of the book, as the other tools return it.
limitNoHow many books to return.

Output Schema

NameRequiredDescriptionDefault
booksNo
statusYes"try_again_later": the service was busy and looked nothing up, so the other fields are absent.
tagProvenanceNoWhere the moods, vibes, pace and genres come from.
retryAfterSecondsNoWith "try_again_later", when known: how long to wait.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"The Shelfclub id of the book, as the other tools return it."New value: +"The ShelfClub id of the book, as the other tools return it."
    • changedOutput schema / properties / books / items / properties / id / description
      Previous value: -"The Shelfclub id of the book."New value: +"The ShelfClub id of the book."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world safety, so the description's added value is the substantive context it supplies: the candidate universe (10,000 most-read books), tag provenance (machine-generated or voted by at least three readers), and the zero-tag failure mode. It does not discuss ordering guarantees or tie-breaking, which would have been the final detail.

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?

Two dense sentences that front-load the core behavior, with the caveat and the return shape following in logical order. The return-field enumeration is somewhat listy, but nothing is wasted filler.

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 two-parameter read tool with full schema coverage, annotations, and an output schema, the description covers everything an agent needs in order to call it and interpret results. It slightly duplicates the output schema by listing returned fields.

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%, so both parameters are already documented, and the baseline is 3. The description reinforces the id semantics ('a given book') and the cap of up to 10 results, but adds no format or syntax detail beyond the schema.

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 (list) plus a precisely scoped resource (books with overlapping mood/vibe/pace/genre tags relative to a given book), including the candidate pool of the 10,000 most-read books. This is clearly distinguishable from siblings like find_books_by_mood or search_books.

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

Usage Guidelines4/5

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

Usage context is clearly implied: call it with a book id when you want recommendations related to that book. It also states an edge-case rule — a book with no tags has no similar books — which helps an agent interpret an empty result rather than retry. No explicit exclusions or named alternatives, so not a 5.

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