Skip to main content
Glama

open_session

Opens a terminal session on a specified host so you can run commands there; the session appears as a tab in Detour.

Instructions

Open a terminal session on a host. The person sees it as a tab in Detour.

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": {
      "host": "<host>"
    },
    "name": "open_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's name, as list_hosts shows it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose one real trait: the person sees the session as a tab in Detour, i.e. this is a user-visible side effect. It omits whether access must be granted first (relevant given the sibling request_access), whether failures occur for unknown/duplicate hosts, and how the session persists.

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 with zero filler, and the core action is front-loaded before the visibility note. Every clause contributes information.

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?

For a session-lifecycle tool with no annotations and no output schema, the description leaves key questions open: what the call returns (a session handle?), prerequisites such as host existence or access approval, and the relationship to close_session. The visibility note is helpful but not enough for an agent to call this confidently in a workflow.

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 coverage is 100% and the single host parameter is documented in-schema as "the host's name, as list_hosts shows it." The description adds nothing about the host parameter, so the baseline 3 applies.

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?

"Open a terminal session on a host" names a specific verb (open) and resource (terminal session), which clearly separates it from close_session and list_sessions by name alone. It stops short of explicitly stating how it differs from run_command or send_input, but the action is unambiguous.

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?

There is no when-to-use guidance: nothing says this must precede run_command/send_input/read_screen, nor what to do if a session already exists. The only contextual hint is that the session is human-visible, which is behavioral rather than a usage rule.

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