Skip to main content
Glama

tnd_start_book_download

Start downloading an entire book and return a job ID to track completion status.

Instructions

下载整本书;创建任务后返回 job_id,使用 tnd_wait_job 轮询完成状态。

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": {
      "book_id": "<book_id>"
    },
    "name": "tnd_start_book_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
book_idYes数字书籍 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavioral trait: this is an asynchronous task creator that returns a job_id rather than the content itself. It says nothing about duplicate-job behavior, failure modes, cost/quota implications, or authentication requirements, which leaves meaningful gaps for an unannotated mutation-style tool.

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?

Two compact clauses, front-loading what the tool does before the follow-up instruction. Every phrase earns its place with no redundancy.

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 single-parameter async-start tool with no output schema, the description covers the essential contract: it returns a job_id and the caller must poll with tnd_wait_job. Only the routing distinction versus the other start_* siblings is missing, which is a modest gap.

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?

Only one parameter (book_id) exists and schema description coverage is 100%, so the schema already documents it as "数字书籍 ID". The description adds no syntax, format, or provenance detail (e.g. that book_id comes from tnd_search_books), so 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?

The description gives a specific verb and resource ("下载整本书" – download the entire book) and distinguishes scope from chapter-level siblings via "整本书", and its tool name embeds the distinction further. It stops short of naming tnd_start_chapter_download or tnd_start_discrete_download explicitly as the narrower alternatives.

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?

It provides a clear next-step instruction ("使用 tnd_wait_job 轮询完成状态"), which is genuinely useful workflow guidance. However, it gives no guidance on when to choose this over tnd_start_chapter_download or tnd_start_discrete_download, and no prerequisites or exclusions are stated.

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