Skip to main content
Glama
Sign In
30book-mcp

30book-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Browse a category, genre, nation, award or tag

sb_browse
Read-onlyIdempotent

Browse books by category, genre, nation, award, or tag to explore a topic instead of keyword search, with paging, sorting, publisher, and stock filters.

Instructions

Books of a category (bta-N-M or btf-N-M-K), genre, nation, award list or tag.

Use to browse a topic instead of a keyword. bts-N sections are not listable. Award pages ignore sort / filters.

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": {
      "kind": "<kind>",
      "key": "<key>"
    },
    "name": "sb_browse"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYescategory: code like 'bta-1-1' (sb_categories); genre / nation / award: id from sb_collections; tag: text, e.g. 'کتاب_های_پرفروش_1404'.
kindYesWhat to open.
pageNoPage from 1.
sortNoOrder; omit for the page default. cheapest / expensive follow list price.
publisher_idNoOnly this publisher.
available_onlyNoOnly books that are in stock.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/open-world, so the safety profile is covered. The description still adds genuinely useful behavior the annotations don't carry: certain section types are not listable, and award pages silently ignore sort and filter parameters — a real gotcha that prevents wasted calls.

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 blocks, zero filler, with the resource scope front-loaded and the caveats second. The telegraphic style ('bts-N sections are not listable') is compact but slightly cryptic for an agent unfamiliar with the code taxonomy.

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 six parameters fully described in the schema and no output schema, the description carries only the burden of routing and caveats, which it does. It could say more about what a result entry looks like or how pagination terminates, but nothing essential to a correct call is missing.

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 the baseline is 3. The description restates the key formats already documented in the schema ('bta-N-M or btf-N-M-K') and adds only the partial caveat that sort/filters are inert on award pages, without explaining the kind-specific key semantics further.

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 a specific resource and scope: books within a category (with code formats 'bta-N-M' / 'btf-N-M-K'), genre, nation, award list or tag. It implicitly separates itself from keyword lookup with 'browse a topic instead of a keyword', though it never names sb_search or sb_categories directly.

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?

It gives an explicit when-to-use rule ('browse a topic instead of a keyword') and two concrete exclusions/caveats: 'bts-N sections are not listable' and 'Award pages ignore sort / filters'. What's missing is naming the actual alternative tools (sb_search, sb_collections, sb_categories) for the non-browsable cases.

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