Skip to main content
Glama

Kill a tmux session

kill_session
Destructive

Terminate a tmux session owned by tmux-mcp while protecting agent and container panes; use force only to end a foreign session.

Instructions

Kill a session. Only sessions owned by tmux-mcp can be killed without force; the pane hosting this container and agent panes are always protected.

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": "<session>"
    },
    "name": "kill_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoAllow killing a foreign session
sessionYesSession name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only mark destructiveHint=true, and the description adds substantive guardrail context beyond that: ownership scoping and the hard protection on the container-hosting pane and agent panes. It does not say what happens to processes running inside the killed session, which is a minor remaining gap.

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, the action first and the safety constraints immediately after. No redundant or filler wording, and every clause conveys information the agent needs before calling.

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 destructive, two-parameter tool with an annotation but no output schema, the description covers ownership, protection, and force adequately. Only the failure mode when targeting a protected pane is left implicit.

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

Parameters4/5

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

Schema coverage is 100%, so both parameters are already documented, making the baseline 3. The description nonetheless reinforces the meaning of `force` by tying it to the ownership rule, which gives the flag more operational context than the schema's one-line note.

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 opens with a specific verb and resource ("Kill a session"), which is unambiguous and clearly distinct from siblings like new_session or list_sessions. It stops short of explicitly naming a sibling to differentiate from, but the action is self-evident.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the governing condition for use: sessions owned by tmux-mcp can be killed without force, implying force is the path for foreign sessions. It does not spell out error behavior or an explicit "do not use for X" case, but the ownership constraint covers the main decision point.

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