Skip to main content
Glama
30book-mcp

30book-mcp

by sepehr071

Books of a publisher

sb_publisher
Read-onlyIdempotent

Retrieve a publisher's books and short about text, with sorting, pagination, and in-stock filtering for bookstore research.

Instructions

One publisher's books plus a short about text. Try sort='bestselling' or 'cheapest'.

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": {
      "publisher_id": "<publisher_id>"
    },
    "name": "sb_publisher"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage from 1.
sortNoOrder; omit for the page default. cheapest / expensive follow list price.
publisher_idYesPublisher id (sb_find_publisher), e.g. 1.
available_onlyNoOnly books that are in stock.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one genuine behavioral fact beyond them: the response includes a short about text alongside the book list, which matters because there is no output schema. It says nothing about pagination limits, result ordering defaults, or how large a page returns.

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 what is returned and followed by a concrete parameter suggestion; no filler or redundancy. The brevity borders on under-specification for a four-parameter tool, but nothing present is wasted.

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

Completeness5/5

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

This is a simple read-only, single-entity listing tool with fully documented parameters and no output schema, so the burden is light. The description covers the entity scope and the one non-obvious return element (the about text), which is enough for an agent to call it correctly.

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 the baseline is 3 and the schema already documents page, sort, publisher_id and available_only. The description's 'Try sort=bestselling or cheapest' only repeats enum values already present in the schema and adds no new meaning about default ordering or how sort interacts with paging.

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 resource and scope: the books belonging to exactly one publisher, plus an accompanying 'about' text. An agent can distinguish it from generic browsing or search siblings because the publisher_id scope is explicit. It stops short of naming the closest sibling (e.g. sb_author for the same query keyed by author), so differentiation is inferred rather than stated.

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 / when-not-to-use guidance and no mention of alternatives such as sb_browse or sb_author. The only guidance ('Try sort=bestselling or cheapest') is a parameter nudge, not a routing rule, so the agent must guess when this tool is preferable to its siblings.

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