Skip to main content
Glama
Sign In
FluxDown

FluxDown

by zerx-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

download_pause

Pause a specific download task by its task ID to temporarily stop the transfer. The task remains listed for later resumption.

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": {
      "taskId": "<taskId>"
    },
    "name": "download_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes任务 ID（必填）。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations provided. Description only states the basic action without disclosing effects like whether pausing is reversible, impact on other tasks, or error states. Minimal behavioral insight for a mutation operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely short (one sentence), which is concise but lacks substantive information. It is front-loaded but too terse to fully serve an AI agent's decision-making.

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?

No output schema exists; description does not mention return values or state changes. For a simple pause operation, it could be acceptable, but it omits details like idempotency or concurrent effects. Incomplete for an agent.

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?

Parameter schema coverage is 100% with a simple required taskId string. The description does not add meaning beyond the schema, but for a single straightforward parameter, this is acceptable. No extra guidance on how to obtain the task ID.

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?

Description clearly states the action (pause) and object (specified task). It distinguishes from sibling tool download_pause_all by focusing on a single task. However, it does not explicitly mention that tasks are download-related, though context from sibling names implies it.

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?

No information on when to use this tool versus alternatives like download_pause_all or download_resume. The description lacks any context about prerequisites or appropriate scenarios.

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

Deploy Server

Other Tools