Skip to main content
Glama

List saved sessions

get_saved_sessions
Read-only

Get list of saved 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": "get_saved_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that: no note on whether all sessions are returned or scoped, no ordering, no mention of whether the list can be empty. With annotations carrying the burden, extra behavioral context would have been the main opportunity here.

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

Conciseness3/5

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

It is a single short sentence with no filler, so nothing is wasted. The flip side is under-specification: the same character count could have carried scope or return-value information, and there is no structure beyond a bare phrase.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read-only list tool with no output schema, the definition is minimally adequate: the agent knows it is safe and takes no arguments. But with no output schema, the description is the only place a reader could learn what a returned session entry looks like (ID, name, timestamp) or how to feed that into resume_saved_session or remove_saved_session, and it says nothing about that.

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 the schema has nothing to explain and the baseline of 4 applies. The description correctly makes no parameter claims rather than inventing filters that do not exist.

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

Purpose3/5

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

"Get list of saved sessions" names a verb (get/list) and a resource (saved sessions), so the basic purpose is retrievable. However, it is essentially a restatement of the title "List saved sessions" and the tool name, offering no distinguishing detail about what a "saved session" contains or how this differs from resume_saved_session or remove_saved_session.

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 the sibling tools (resume_saved_session, remove_saved_session) that operate on the same resource, and no stated preconditions. The only usage signal is implicit: an agent infers this is the discovery step before resuming or removing a session.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources