Skip to main content
Glama
Sign In
wb-cursor-bridge

wb-cursor-bridge

by jsyzc2019
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

cursor_cancel

Cancel a running Cursor CLI job and terminate its entire process tree by job ID, stopping stuck or unwanted code tasks and their child processes.

Instructions

Cancel a running job and kill its entire process tree.

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": {
      "jobId": "<jobId>"
    },
    "name": "cursor_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/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; it does valuable work by disclosing that cancellation kills the entire process tree, i.e. that this is destructive and broader than a single process. It omits irreversibility, whether confirmation is required, and behavior when the job is already finished or unknown.

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?

One short sentence with the destructive scope front-loaded; there is no filler and every clause earns its place.

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?

With no annotations and no output schema, the description should explain the sole required parameter and the effect of an unsuccessful cancel. It covers the destructive scope well but leaves the parameter entirely undocumented, which is the main gap for a one-parameter mutation tool.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter 'jobId' has no description in the schema or the description text. The agent is not told where to obtain a jobId (presumably from cursor_run or cursor_list) or whether partial IDs are accepted.

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?

States a specific verb ('Cancel') and resource ('a running job') and adds scope ('entire process tree'). It is clearly distinct from siblings like cursor_run or cursor_status, though it never names them explicitly.

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?

The phrase 'a running job' hints that the target must be active, but there is no explicit when/when-not guidance, no mention of alternatives such as cursor_status for checking state first, and no prerequisites or confirmation expectations.

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