Skip to main content
Glama

list_sessions

Read-only

Reads reachable local Claude and Codex session metadata so agents can discover available sessions without sending messages or reading transcripts.

Instructions

Read reachable local Claude and Codex session metadata. Does not send messages or read transcripts. Warnings explain inaccessible endpoints.

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

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds local-only scope, confirms no transcript content is exposed, and warns that inaccessible endpoints surface as warnings. It does not describe the shape of returned metadata, though the tool takes no arguments and has no output schema to rely on.

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?

Three short sentences, each carrying distinct information: the read scope goes first, then the exclusion, then error behavior. No redundancy or filler.

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?

For a no-argument, read-only list tool, the description covers scope, exclusions, and warning behavior, which is enough to call it correctly. It leaves 'session' and 'reachable endpoint' somewhat undefined, so an agent does not know exactly what entities or forms of session (live vs. persisted) it will see.

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 schema is effectively complete. Baseline of 4 applies.

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?

States a specific verb ('Read') and a specific resource ('reachable local Claude and Codex session metadata'), scoping it to local endpoints. The negative clause 'Does not send messages or read transcripts' differentiates it from the messaging siblings without ambiguity.

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 exclusion of sending messages and reading transcripts implicitly routes the agent to send_message/read_messages for those needs, which is clear contextual guidance. It never states an explicit 'use this when' trigger or names the alternatives directly, so it falls short of a full when/when-not pair.

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