Skip to main content
Glama
30book-mcp

30book-mcp

by sepehr071

Similar books and more by the author

sb_similar
Read-onlyIdempotent

Find similar books and up to 20 additional titles by the same author or translator using a book ID; use sb_search for other editions.

Instructions

Similar books, more by the author and by the translator, up to 20 each. Other editions: use sb_search.

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": {
      "book_id": "<book_id>"
    },
    "name": "sb_similar"
  }
}

Input Schema

NameRequiredDescriptionDefault
book_idYesBook id from sb_search / listings, e.g. 167515.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds a real behavioral fact those annotations do not carry: results are capped at up to 20 items per category. It says nothing about ordering or whether more results can be fetched, which keeps it short of a 5.

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 short sentences, front-loaded with the return scope followed by the redirect. The telegraphic fragment style is slightly terse but wastes nothing; every clause carries information.

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 simple single-parameter read tool with no output schema, the description covers what is returned, how many items per category, and where to go for a related need. Missing only finer details like ordering or whether results are paginated, which are minor at 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 coverage is 100% and the single book_id parameter is already documented with bounds, an example, and its source. The description adds no further meaning about the parameter, so the baseline of 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?

The description names the resource and the three result categories it returns (similar books, more by author, more by translator), which is more specific than the title alone. The verb is implicit, but an agent can tell this is a related-books lookup distinct from a general search.

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?

One explicit routing rule is given: other editions should go through sb_search. There is no guidance on when to prefer this over sb_book or sb_author, nor any stated prerequisites beyond the book_id, so usage is only partially framed.

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