Skip to main content
Glama

Top Books

top_books
Read-onlyIdempotent

Apple Books chart, read from Apple's RSS Marketing Tools feed, the top-free (default) or top-paid ebooks in one storefront country, up to 100 entries. Each entry returns the book title, author, Apple id, genres, release date, artwork URL and Apple Books link. Answers which ebooks are topping the Apple Books charts today.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 25,
      "country": "us",
      "free_or_paid": "top-paid-books"
    },
    "name": "top_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
countryNo
free_or_paidNotop-free | top-paid (default top-free)

Output Schema

NameRequiredDescriptionDefault
feedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the upstream feed, the 100-entry cap, and the exact fields returned per entry.

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 dense sentences, front-loaded with the resource and source, then the return shape and the question it answers. Slightly packed but no filler sentences.

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?

An output schema exists, yet the description still summarizes the returned fields, and it covers source, scope, defaults and limits. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 33% schema coverage, the description compensates well: it clarifies that free_or_paid defaults to top-free, that country selects a single storefront, and that limit caps at 100 entries. It does not state the country code format (e.g. 'us'), which is the main remaining gap.

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

Purpose5/5

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

States a specific verb and resource ('Apple Books chart... top-free or top-paid ebooks in one storefront country') plus the data source (Apple's RSS Marketing Tools feed), which cleanly separates it from siblings like top_movies and itunes_search_top_podcasts.

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 description implies the use case ('Answers which ebooks are topping the Apple Books charts today') and notes the default mode, but gives no explicit when-to-use vs when-not guidance and never references an alternative tool for related queries.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.