Skip to main content
Glama

List terminal sessions

session_list
Read-only

List every terminal session this server started, showing its name, sandbox status, start time, and current activity such as a running job, exit code, or foreground program. Read-only.

Instructions

List the sessions this server started: each one's name, whether it is sandboxed, when it started, and what it is doing (job running, job exited N, or the program in the foreground). Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the trailing 'Read-only.' is redundant. However, the description adds real value the annotations don't: it discloses the per-entry fields (name, sandboxed flag, start time) and spells out the possible activity states ('job running, job exited N, or the program in the foreground'), which is the kind of return-shape detail an agent needs.

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

Conciseness4/5

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

The verb and scope are front-loaded in a single dense sentence, and the parenthetical state list is compact rather than sprawling. The only waste is the standalone 'Read-only.' sentence, which merely restates the readOnlyHint annotation.

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?

With no output schema and no annotations explaining return values, the description carries the burden and does so by describing the entry shape and activity states. It leaves minor gaps such as ordering and whether terminated sessions are included, but an agent has enough to call and interpret it.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies no filtering arguments are needed.

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?

The description uses a specific verb and resource ('List the sessions') and scopes it to 'this server started', then enumerates exactly what each entry contains. That enumeration implicitly separates it from session_read (one session's output) and session_send, but it never names a sibling to route the agent explicitly, so it falls just short of a 5.

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?

Usage is only implied: an agent can infer this is the discovery step before session_read or session_send. There is no explicit 'use this when...' statement, no exclusion, and no mention of whether finished sessions appear in the list.

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