Skip to main content
Glama
30book-mcp

30book-mcp

by sepehr071

Discounted books

sb_deals
Read-onlyIdempotent

Find books with large discounts from bestseller lists, optionally filtered by subject or stock, and compare final prices to avoid inflated publisher list prices.

Instructions

Best sellers (or one subject) by biggest discount. Some publishers inflate list prices: compare final_price.

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_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage from 1.
subjectNoSubject code such as 'bta-1-1'; omit for all best sellers.
available_onlyNoOnly books that are in stock.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety, idempotency, and open-world behavior, so the description mainly adds domain context. The warning that some publishers inflate list prices and that final_price should be compared is genuinely useful behavioral guidance beyond the structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences, front-loads the core purpose, and immediately follows with a useful caveat. There is no unnecessary wording or repetition.

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?

For a simple read-only listing tool with full schema coverage and rich annotations, the description gives enough functional context and a practical price caveat. It does not describe output format or pagination, but the schema and annotations carry most of that burden.

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 page, subject, and available_only are already fully documented in the input schema. The description reminds the agent that subject is optional via 'or one subject', but adds little parameter meaning beyond the schema.

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 clearly states the tool returns best sellers, optionally within one subject, ordered by biggest discount. It is specific enough to understand the resource and ranking, though it does not explicitly contrast itself with sibling tools such as sb_bestsellers.

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

Usage Guidelines3/5

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

The phrase 'Best sellers (or one subject) by biggest discount' implies when the tool is useful: finding discounted bestsellers rather than general search or browsing. However, it names no alternatives and gives no explicit when-not-to-use guidance.

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