Skip to main content
Glama

Cancel

tm_operation_cancel
DestructiveIdempotent

Cancel an ongoing Tunnel Manager operation by its operation ID to stop work and clean up the session. Use it when a tracked operation must be aborted safely.

Instructions

Cancel (tm_operations). Operation lifecycle and session management.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tm_operation_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoConfirm a destructive action (cancel) without elicitation.
detailsNoAdditional details (start).
total_stepsNoTotal steps (start).
operation_idNoOperation ID (get_progress/cancel/get_metrics).
operation_typeNoType of operation (start).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.4.7
    • addedInput schema / properties / confirm
      Added value: +{
      +  "default": false,
      +  "description": "Confirm a destructive action (cancel) without elicitation.",
      +  "type": "boolean"
      +}
  2. Addedv3.3.1

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is known. The description adds nothing on top: it does not say what state is destroyed, whether in-flight sessions are terminated, whether confirmation is required, or how the call behaves if the operation already finished.

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

Conciseness2/5

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

Two short fragments, and the second one ("Operation lifecycle and session management") conveys no actionable information. Brevity without content counts against it rather than for it.

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?

An output schema exists, so return values need not be explained, and the annotations cover the safety profile. However, for a destructive, idempotent operation on a 5-parameter merged schema, the description omits the essentials: target identification, confirmation behaviour, and post-cancel state.

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 100%, which sets a baseline of 3, but this is a merged schema where only operation_id and confirm are relevant to cancel while details, total_steps and operation_type are tagged "(start)". The description does nothing to disambiguate which parameters apply here, which is exactly the gap it could have filled.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ("Cancel") tied to the tm_operations namespace, so the action is identifiable, but it never states what is being cancelled (an operation identified by operation_id) or what cancelling does. The trailing phrase "Operation lifecycle and session management" is category-level filler that does not sharpen the purpose or separate it from tm_operation_start, tm_operation_get_progress, or tm_operation_list_sessions.

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?

There is no when-to-use guidance, no mention of preconditions such as needing a valid operation_id, and no pointer to alternatives like tm_operation_get_progress to check status first. The only usage hint anywhere is buried in the schema's confirm parameter, not in the description.

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