tmux-mcp-server

by manhnv198669

Overview Schema Source Related Servers Discussions Admin

create_session

Creates a new detached tmux session with optional name, dimensions, and start directory, enabling programmatic session setup and control.

Instructions

Create a new detached tmux session

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

Input Schema

Name	Required	Description	Default
`name`	No
`width`	No
`height`	No
`start_directory`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 12, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false and idempotentHint=false, covering the safety profile. The description adds the valuable detail that the session is created 'detached', but it does not disclose behaviors like name conflict handling or side effects beyond creation. The description does not contradict annotations.

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?

The description is a single, front-loaded sentence with no filler or repetition. It is appropriately sized for the simple operation it describes, earning its place without wasted words.

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?

Despite having annotations and an output schema, the description is too sparse for a mutation tool with 4 parameters and no parameter descriptions. It omits any contextual details about how the session is created, what 'detached' implies, or what the response contains, making it incomplete for an agent to use confidently.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention any of the parameters (name, width, height, start_directory) or their meanings. The agent cannot infer parameter semantics from the description, leaving a significant gap.

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 'Create a new detached tmux session' uses a specific verb ('Create') and resource ('tmux session'), clearly distinguishing it from sibling tools like create_window. It also specifies an important attribute ('detached') that sets expectations for what the tool does.

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?

No guidance is provided on when to use this tool versus alternatives like list_sessions or get_session, nor any prerequisites (e.g., server availability) or exclusions. The purpose is clear, but the description does not help the agent decide when to invoke it.

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