Skip to main content
Glama

list_sessions

Retrieves all currently open SSH sessions in Detour so you can identify active approved hosts and scopes before running commands, editing files, or starting tunnels.

Instructions

Your open sessions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior1/5

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

With no annotations supplied, the description carries the full behavioral burden and fails to meet it. It does not say the tool is read-only, whether it requires an established connection or access approval (cf. request_access/wait_for_access siblings), whether results are paginated or filtered, or what the returned session entries look like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three words are not wasteful, but this is under-specification rather than conciseness — the fragment lacks a verb and any structure an agent can act on. It is front-loaded only in the trivial sense that there is nothing else to follow.

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 zero-parameter listing tool with no annotations and no output schema, the description must at minimum convey what a session is and what fields come back. Neither is provided, so the agent must reconstruct behavior from sibling names alone.

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

Parameters4/5

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

The input schema declares zero parameters at 100% coverage, so there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter meaning is missing because no parameters exist.

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

Purpose2/5

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

The text 'Your open sessions.' is essentially a restatement of the tool name list_sessions, with no verb and no scope detail. It does imply that only currently open sessions (not closed ones) are returned, which is marginally more than a pure tautology, but it gives no indication of what a 'session' contains or how this differs from siblings like list_hosts or list_dir.

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, no mention of alternatives such as list_dir or close_session, and no stated prerequisites. The agent is left to infer usage entirely from the tool name and the surrounding catalog.

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