Skip to main content
Glama
Sign In
30book-mcp

30book-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Books of an author or translator

sb_author
Read-onlyIdempotent

Lists books by a specific author or translator, with pagination, sorting, and in-stock filtering for bookstore browsing.

Instructions

Books by one author or translator (default newest first).

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": {
      "person_id": "<person_id>"
    },
    "name": "sb_author"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description contributes one genuinely useful behavioral fact beyond that: results default to newest-first ordering. It adds nothing about result volume, pagination behavior, or how translator matches are distinguished from author matches.

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 front-loaded sentence with zero filler; the resource and the default ordering are both stated immediately. It is arguably terse to the point of under-specification, but no sentence or clause is wasted.

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

Completeness3/5

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

With 100% schema coverage and full annotations, the structured data carries most of the burden, and there is no output schema to explain. Still, for a list tool the description says nothing about the shape or size of the returned list (e.g., page size, total counts), leaving the agent to discover result format empirically.

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 all four parameters are already documented, including the sort enum and the 'cheapest / expensive follow list price' note. The description's only added semantics is confirming the default sort is newest-first, which is a marginal supplement to the schema's 'omit for the page default'.

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 relationship: books filtered to one author or translator. An agent can distinguish it from sb_book (a single book) or sb_search (query-based) without opening the schema, though the description never names those siblings explicitly.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The agent must infer from the phrase 'by one author or translator' that this is the lookup to use once a person_id is known (e.g., after sb_find_person), which is implied rather than stated.

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