Skip to main content
Glama

workbuddy_cancel

Request cancellation of an active WorkBuddy conversation by session ID. Stops an in-progress task without undoing actions already completed.

Instructions

Request cancellation of a WorkBuddy conversation; does not undo past actions.

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": {
      "session_id": "<session_id>"
    },
    "name": "workbuddy_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 usefully discloses that past actions are not rolled back, and the phrase 'Request cancellation' hints the operation is best-effort rather than instantaneous. It does not say whether cancellation is immediate or queued, what terminal state the session lands in, or whether it requires ownership of the session.

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 core action front-loaded and the critical caveat appended as a clause. Nothing is wasted and nothing buries the main point.

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?

An output schema exists, so return values need not be explained, and the tool is structurally simple with one parameter. But with zero annotations the description should still cover permission/ownership requirements and cancellation outcomes; it covers only the non-rollback caveat.

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% for the single required parameter, and the description never mentions session_id — not what it identifies, how to obtain it, or whether it must reference a currently running conversation. The description adds no meaning beyond the bare schema property name.

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 and resource: 'Request cancellation of a WorkBuddy conversation.' That is clearly distinct from siblings like workbuddy_continue, workbuddy_run, and workbuddy_status, though the description never explicitly contrasts itself with them.

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 when-to-use guidance, no preconditions (e.g. session must be active), and no mention of alternatives such as checking workbuddy_status before cancelling. The only usage signal is the name and the verb 'Request', so the agent must infer context.

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