Skip to main content
Glama
Sign In
claude-orchestrator

claude-orchestrator

by lilyjem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

stop_task

Stop a running task. Enable cleanup to also remove it from the registry and CLI.

Instructions

停止运行中的任务。cleanup=true 时同时从注册表和 CLI 中移除。

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": {
      "task_id": "<task_id>"
    },
    "name": "stop_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
cleanupNo是否同时清理，默认 false
task_idYes任务 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the cleanup=true side effect of removing the task from the registry and CLI, but it does not explain reversibility, error behavior, or consequences for tasks that are not running.

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 description is extremely compact, front-loads the core action, and then adds the conditional cleanup detail. Every word contributes value with no redundancy.

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 simple 2-parameter tool, the description covers the core action and the cleanup option, but with no output schema and no annotations it omits return/error behavior and edge cases such as stopping a task that is not running. The description is adequate but not fully complete.

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

Parameters4/5

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

Schema coverage is 100%, which gives a baseline of 3. The description adds concrete meaning beyond the schema by specifying that cleanup=true removes the task from the registry and CLI, which is more informative than the schema's generic '是否同时清理' phrasing.

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 states a specific verb ('stop') and a specific resource ('running task'), and it adds the cleanup behavior. This clearly distinguishes it from sibling tools like dispatch_task, get_task_status, and list_tasks.

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 description implies this tool is for stopping a running task, but it does not explicitly say when to use it versus alternatives, nor does it mention exclusions such as already-stopped or completed tasks. No alternative routing is provided.

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