Skip to main content
Glama

get_book_chart

Read-only

Fetch Douban book charts for fiction, non-fiction, or new releases with an optional count to browse current rankings.

Instructions

获取图书榜单。kind: fiction (小说)、non_fiction (随笔)、new (新书速递)。

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": {
      "kind": "<kind>"
    },
    "name": "get_book_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0-alpha.0

TDQS

C2.9/5.0
Behavior2/5

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

The readOnlyHint annotation already covers the safety profile, so the description's only remaining job is to say something about the operation itself — ranking basis, time window, ordering, or result shape — and it says none of that. It contributes only value-label translations for the enum, which is parameter-level rather than behavioral information.

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 sentences, zero filler, with the core action front-loaded before the enum glosses. The terseness is efficient rather than padded, though the enum list is presented without any framing sentence that would make the structure read more clearly.

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 no output schema, the description should convey at least minimally what a 'chart' returns (ordered list of books, how many, over what period), and it does not. Given the tool's low complexity and the readOnlyHint annotation the gap is not severe, but an agent still cannot predict the response.

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 0%, so the description must carry parameter meaning. It does well on the required 'kind' parameter by glossing the three opaque enum values (fiction=小说, non_fiction=随笔, new=新书速递), but the 'count' parameter (default 10, min 1, max 20) is never mentioned, leaving half the parameters undocumented anywhere.

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 opens with a specific verb+resource (获取图书榜单 = fetch the book chart/ranking), which cleanly separates it from siblings like get_book, get_book_reviews, and search_book. It never explicitly names an alternative, so it stops short of a 5, but the purpose is unambiguous.

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 guidance at all: nothing says to call this for browsing popular titles versus using search_book for a targeted lookup or get_book for details on one title. The only implied usage comes from the word 榜单 (chart/ranking) itself.

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