Skip to main content
Glama

tnd_search_books

Search global Tomato book metadata by book title or author keyword to locate titles for download or inspection. It only searches and does not manage subscriptions.

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": "tnd_search_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes书名或作者关键词

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the safety profile, and it does signal a non-mutating, search-only operation. It does not disclose result volume, pagination, ranking, or whether results are cached/remote, which matters for a global search across an unknown corpus.

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 tight clauses, front-loaded with the search scope followed by the exclusion. No filler, though the second clause is a constraint rather than a usage route.

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?

For a one-parameter search with no output schema, the agent still lacks any sense of the return shape (list of books? metadata fields?) or result limits. The definition is adequate to call the tool but not to predict its output.

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 coverage is 100% and the single parameter q already documents '书名或作者关键词'. The description adds nothing about matching behavior (exact vs fuzzy, multi-term, language), so the baseline 3 applies.

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?

States a specific verb (搜索) and resource (番茄书籍元数据) plus a global scope (全局), which tells the agent exactly what domain is queried. It does not name any sibling (e.g. tnd_preview_book or tnd_get_library) to sharpen the boundary, so it stops short of a 5.

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 clause '本工具只搜索,不管理订阅' gives a negative boundary — this is a lookup, not a subscription or download action — which is useful given the download-heavy sibling set. However, it never says when to prefer it over tnd_preview_book or tnd_get_library, leaving the alternative choice to inference.

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