Skip to main content
Glama

Interrupt Command By Id

interrupt_command_by_id

Stops a running asynchronous SSH command by sending Ctrl+C using its command ID, allowing long-running tasks to be interrupted when no longer needed.

Instructions

Interrupt a running async command by sending Ctrl+C.

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": {
      "command_id": "<command_id>"
    },
    "name": "interrupt_command_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
command_idYesThe command ID returned by execute_command_async

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2+p1

TDQS

A3.5/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 delivery mechanism (Ctrl+C, i.e., an interrupt signal rather than a hard kill), which is meaningful behavior beyond the name. However, it says nothing about what happens on failure (unknown or already-exited command ID), whether the process is guaranteed to terminate, or what the call returns.

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, front-loaded with the action and effect, with zero filler. Nothing is wasted and nothing important is buried.

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 one-parameter tool this covers the core, but with no annotations and no output schema the description should say more about post-call state and error behavior. It is minimally sufficient rather than complete.

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 description coverage is 100% and the single parameter already documents that it is 'the command ID returned by execute_command_async'. The description adds no additional meaning about the ID format or lifetime, so 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?

States a specific verb ('Interrupt') and resource ('a running async command') and adds the mechanism ('sending Ctrl+C'), so the effect is unambiguous. It is not explicitly differentiated from siblings like send_input or send_keys, which could also deliver a control character, but the intent is clear.

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 phrase 'running async command' implies the preconditions: the command must still be executing and must have come from execute_command_async. There is no explicit when-not guidance (e.g., what to do for a command that already finished, or how this differs from close_session) and no named alternative.

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