Skip to main content
Glama

search_book

Read-only

Search Douban books by keyword to find titles, authors, and ratings. Use it to locate specific books or discover related titles for research and recommendations.

Instructions

按关键词搜索豆瓣图书。

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": {
      "q": "<q>"
    },
    "name": "search_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes
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

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered without the description. Beyond that the description adds nothing: no mention of result ordering, whether the search is remote/rate-limited, or how results relate to the count cap, leaving the behavioral picture entirely to structured fields.

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 no filler or redundancy. It is efficient rather than padded, though the brevity crosses into under-specification given the tool has a non-trivial count parameter.

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 two-parameter, no-output-schema tool the description is the only place to explain the count cap and the shape of returned results, and it does neither. An agent can invoke it, but cannot predict result volume or content from the definition.

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 carries weight for the two parameters. It does explain q as a keyword query, which is real added meaning, but count (default 10, max 20) is never mentioned despite being the one parameter whose purpose is genuinely non-obvious; only the schema's min/max/default hint at it.

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 sentence pairs a specific verb (搜索/search) with a specific resource (豆瓣图书/Douban books) and a scoping mechanism (按关键词/by keyword), so the agent can tell it apart from get_book or get_book_reviews by name alone. It stops short of explicitly contrasting itself with those siblings, keeping it out of 5 territory.

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?

Usage is only implied: an agent can infer this is the lookup path when starting from a keyword rather than a known book id. There is no statement of when to prefer get_book instead, no note on what happens with empty or no-match results, and no exclusions.

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