Skip to main content
Glama
30book-mcp

30book-mcp

by sepehr071

New releases

sb_new_releases
Read-onlyIdempotent

Fetches newly released printed books from an Iranian bookstore, page by page. Filter to in-stock titles only to browse available new arrivals.

Instructions

Newest books (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_new_releases"
  }
}

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, idempotentHint and openWorldHint, so the description need only add context. The one addition, "(10 pages)", is ambiguous — it could mean page size of 10 results or a hard cap of 10 pages — and it does not clarify ordering (by date? descending?) or what happens at the page=500 boundary.

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 phrase that is front-loaded, with no filler sentences. Its brevity is efficient, though the parenthetical is too compressed to be informative.

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 tool with no output schema and no annotations explaining results, the definition should say what a returned item contains and what the paging window is. Neither is covered, leaving the agent under-informed about result shape and ordering.

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% and both parameters (page, available_only) are documented there, so the baseline is 3. The description adds nothing beyond the schema and does not explain how availability filtering interacts with the 'newest' ordering.

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?

"Newest books" names the resource and implies a list-style read, but the verb is implicit and nothing distinguishes it from siblings like sb_bestsellers or sb_deals, which could also surface recent or featured titles.

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?

No when-to-use guidance is given and no alternative is named. An agent must infer on its own whether this or sb_bestsellers/sb_search is the right call for finding recent books.

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