Skip to main content
Glama
brkhrdt
by brkhrdt

start_session

Initiate a new PTY session with any command or shell, returning a session ID for subsequent operations.

Instructions

Start a new PTY session with any command or shell. Returns a session_id to use with other commands.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory for the session
argsNoOptional explicit arguments for the command. If omitted, arguments are parsed from the command string. Use this for arguments with spaces or special characters.
commandNoCommand/binary to execute (default: $SHELL or /bin/bash). Can be 'python3', 'somebinary -a -b', etc. Arguments are auto-parsed from the command string if 'args' is not provided.
buffer_sizeNoScrollback buffer size in lines (default: 1000)
timeout_sessionNoIdle timeout in seconds (default: 86400)
sentinel_commandNoCommand template to echo sentinel. Use {sentinel} placeholder. Default: 'echo {sentinel}'. For Python REPL: "print('{sentinel}')"
Behavior3/5

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

No annotations are provided, so the description must carry full burden. It mentions starting a PTY session and returning an ID, but does not disclose resource allocation, idle timeout behavior (though parameters hint at it), or other side effects.

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 two sentences long, front-loaded with the purpose, and contains no wasted words.

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?

Given the complexity (6 parameters, no output schema, no annotations), the description provides enough high-level context about starting a session and linking to other tools. The schema covers parameter details adequately.

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%, so the description adds no additional meaning beyond the schema. It does not elaborate on parameters like cwd, args, or sentinel_command.

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 'Start', resource 'PTY session', and the return value 'session_id'. It distinguishes well from sibling tools like list_sessions and stop_session.

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 implies that this tool is the first step to get a session_id for other commands, but it does not explicitly exclude alternatives or mention when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/brkhrdt/pty-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server