Skip to main content
Glama
Sign In
tmux-mcp

tmux-mcp

by fr1sk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

new_window

Create a new window in any tmux session, with optional working directory, window name, and initial command.

Instructions

Create a new window in an existing tmux session.

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": "new_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoWorking directory for the new window.
nameNoWindow name.
commandNoShell command to run immediately. WARNING: executes in your shell.
sessionYesSession name to create the window in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided. Description lacks behavioral details beyond the basic action. Contains a useful warning about the command parameter executing in the shell, but does not disclose if destructive, what happens to existing windows, or auth requirements.

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?

Single sentence plus a warning. No unnecessary words. Efficient and front-loaded.

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?

Tool creates windows with side effects but no output schema. Description lacks explanation of return behavior or what happens after creation (e.g., focus, attachment). Missing details for a non-trivial creation tool.

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 descriptions cover all parameters (100% coverage). Description adds the command warning but does not elaborate on other parameters beyond repeating schema. Baseline 3 achieved.

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?

Clear verb 'create' and resource 'window' with context 'in an existing tmux session'. Distinguishes from sibling tools like 'new_session' and 'split_pane'.

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?

Description implies usage (requires existing session) but does not explicitly state when to use vs alternatives like split_pane or new_session. No when-not guidance.

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