Skip to main content
Glama
Sign In
tmux-mcp

tmux-mcp

by fr1sk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

kill_session

Terminate a tmux session and remove all its windows and panes. Requires user confirmation as this action cannot be undone.

Instructions

Kill a tmux session and all its windows and panes. ALWAYS confirm with the user before calling — this is destructive and cannot be undone.

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
sessionYesSession name to kill.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description fully discloses the destructive, irreversible nature of the tool and that it kills all windows and panes. This is sufficient for an agent to understand the impact.

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 sentences: one for purpose, one for critical usage note. No redundant information; every sentence earns its place.

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 simple single-parameter tool with no output schema, the description covers purpose, destructiveness, and the need for confirmation. It is nearly complete; minor gap: no description of the return value or confirmation mechanism.

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?

The description does not add information beyond the schema for the single parameter 'session'. Since schema coverage is 100%, a baseline of 3 is appropriate. No additional semantic detail is provided.

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

Purpose5/5

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

The description clearly states the verb 'Kill' and the resource 'tmux session', including the scope 'all its windows and panes'. This distinguishes it from sibling tools like kill_window and kill_pane, which target narrower scope.

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?

The description explicitly warns 'ALWAYS confirm with the user before calling — this is destructive and cannot be undone', providing strong usage guidance. It does not explicitly compare to alternatives, but the context of sibling tools implies when to use this vs. kill_window/kill_pane.

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