Skip to main content
Glama

tnd_start_discrete_downloads

Starts batch downloads for selected chapters using 1-based catalog indexes or item IDs, skips chapters with existing text, and merges consecutive selections into background range tasks.

Instructions

批量下载指定章节;indexes 为 1-based 在线目录位置,与 item_ids 二选一。跳过已有正文,连续位置合并为区间任务,后台顺序执行。

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_discrete_downloads"
  }
}

Input Schema

NameRequiredDescriptionDefault
book_idYes数字书籍 ID
indexesNo离散章节位置,1-based;与 item_ids 二选一
item_idsNo章节 item_id;与 indexes 二选一

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A5/5.0
Behavior5/5

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

Since no annotations are provided, the description carries the entire behavioral burden. It explicitly details complex operational traits like 1-based indexing, merging continuous location tasks into intervals, and background processing.

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?

The definition is highly dense and efficient. It packs all essential functional requirements—input format, exclusivity, execution logic—into a single, powerful sentence without any superfluous wording.

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?

Given the tool's complexity (handling discrete, possibly overlapping, and sequential chapter downloads), the definition is exceptionally complete. It informs the user of the necessary logical assumptions and execution environment required for correct usage.

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

Parameters5/5

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

While the schema defines the parameters, the description reinforces crucial semantic constraints: that indexes are 1-based, and that indexes and item_ids are mutually exclusive, adding clarity beyond the list format.

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?

The description clearly states the tool's purpose using a specific verb and resource: '批量下载指定章节' (Batch download specified chapters). It defines the scope and identifies the action being taken.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides critical usage guidance by detailing input constraints (indexes vs item_ids must be chosen) and execution flow (skipping existing content and sequential execution), which helps distinguish it from broader bulk download tools.

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