Skip to main content
Glama
Sign In
30book-mcp

30book-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search books

sb_search
Read-onlyIdempotent

Search books by title, filter by author, publisher, translator, or stock, and sort by price to compare editions and find the right printed book.

Instructions

Search books by title.

Use first for any book question. Editions are separate books: compare final_price. Next: sb_book.

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": {
      "query": "<query>"
    },
    "name": "sb_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage from 1.
sortNoOrder; omit for the page default. cheapest / expensive follow list price.
queryYesTitle words, Persian, e.g. 'شازده کوچولو'.
extendedNoMatch words, not the exact phrase (more results).
author_idNoAuthor id (sb_find_person).
publisher_idNoPublisher id (sb_find_publisher).
translator_idNoTranslator id.
available_onlyNoOnly books that are in stock.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds one genuinely non-obvious domain fact: editions are separate books and final_price should be compared. It says nothing about result volume, paging behavior, or what an empty result means, so value beyond annotations is real but thin.

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?

Three short sentences, front-loaded with the core action and the routing rule, with zero filler. The trailing fragment 'Next: sb_book.' is terse to the point of being slightly clipped, but nothing is wasted.

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?

With 8 parameters but full schema documentation and annotations, the remaining burden is mainly return-shape context; the description partially covers this by revealing that editions appear as separate results carrying final_price. Pagination and result ordering are left implicit, which is a minor gap for a search tool with a page parameter.

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 every parameter is already documented in the schema. The description adds no meaning beyond it and in fact narrows the mental model to title-only search, leaving the filter parameters and sort semantics entirely to the schema. Baseline 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?

States a specific verb and resource ('Search books by title') and names the follow-up sibling sb_book, so an agent can place it relative to the catalog tools. It slightly understates scope, since the schema supports author/publisher/translator/stock filters, not just title lookup.

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?

'Use first for any book question' gives an explicit entry-point rule, and 'Next: sb_book' prescribes the follow-up. It stops short of stating when to skip this tool (e.g., browsing by category or author page flows), so no exclusions are given.

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

Deploy Server

Other Tools