Skip to main content
Glama
30book-mcp

30book-mcp

by sepehr071

Best sellers

sb_bestsellers
Read-onlyIdempotent

Retrieve site-wide best-selling printed books from an Iranian bookstore, paginated across 10 pages, with an option to filter for in-stock titles only.

Instructions

Site-wide best sellers (10 pages).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sb_bestsellers"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage from 1.
available_onlyNoOnly books that are in stock.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The only added behavioral element is "(10 pages)", which is ambiguous — it could mean the catalog is 10 pages deep or pagination is capped — and it conflicts with the schema's page maximum of 500, leaving the agent unsure how far paging actually goes.

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?

A single short fragment, front-loaded with the resource and scope, with zero filler. Its brevity is efficient, though it is under-specified rather than tight, which is penalized in the other dimensions.

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

Completeness2/5

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

For a simple two-parameter list tool with no output schema, the description still omits what a best-seller entry contains, how ranking is determined, and whether the 10-page limit is real. The agent can call it, but cannot predict results or reconcile the page cap with the schema.

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 both parameters (page, available_only) are already fully documented, establishing a baseline of 3. The description adds no meaning about paging semantics and its "(10 pages)" note actually sits uneasily with the schema's maximum of 500 for page, so it does not help the agent interpret the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Site-wide best sellers" names a resource and a scope, which is slightly more than the title alone, but it largely restates the name/title and never separates this from siblings like sb_new_releases, sb_deals, or sb_browse. An agent knows it returns a ranked list of popular books but not how that ranking is defined or how it differs from adjacent list tools.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no alternative tool is named. The agent must guess whether this or sb_new_releases / sb_deals is the right choice for a 'what's popular' intent.

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