Skip to main content
Glama
Node Mantis

Node Mantis

Official

Cancel a task

cancel_task
Idempotent

Stop a running task and close its browser; tasks that already finished remain unchanged.

Instructions

Stop a running task and close its browser. A task that already finished is left unchanged.

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

Input Schema

NameRequiredDescriptionDefault
task_idYesThe task_id returned by run_task or retrieve_data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.9

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the bar is lower, but the description still adds real context: the browser is closed as a side effect, and a task that already finished is left unchanged. That clarifies both the blast radius and the idempotent behavior in plain terms.

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 short sentences with the primary action front-loaded and the edge case second. Nothing is wasted or redundant.

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 one-parameter mutation tool with annotations covering safety and idempotency, the description covers purpose, side effect, and the finished-task edge case. It could note what happens to task results or in-flight data, but nothing essential to calling it correctly is missing.

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 task_id parameter is documented in the schema as coming from run_task or retrieve_data. The description adds no further meaning about the identifier, 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?

The description states a specific verb and resource ('Stop a running task') and names the concrete side effect ('close its browser'). It is clearly distinct from siblings like get_task or run_task, though it does not explicitly contrast itself with them by name.

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?

Usage is implied by 'Stop a running task,' and the second sentence gives a no-op condition for already-finished tasks. However, it never states when an agent should prefer this over checking status with get_task first, nor any prerequisites or alternative.

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