Skip to main content
Glama

list_cache_sessions

Read-only

Lists locally recorded chat sessions with token-weighted cache summaries, excluding conversation text. Optionally include hidden internal review sessions.

Instructions

List locally recorded chats and token-weighted cache summaries. Conversation text is excluded.

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_cache_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_internalNoInclude internal automatic review sessions (hidden by default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered without the description. The description does add one valuable behavioral fact beyond them: conversation text is excluded and data is locally recorded, which tells the agent about privacy and scope. However, it says nothing about ordering, pagination, or size of results.

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 content summary is front-loaded before the exclusion note. Every clause carries information.

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 read-only list tool with no output schema and a trivial single-parameter input, the description covers scope, localness, and excluded content adequately. It could say slightly more about what a session record contains, but nothing critical is missing.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already explains include_internal and its default. The description adds nothing about this flag, which is the expected baseline when the schema is self-documenting.

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?

States a specific verb (list) and resources (locally recorded chats and token-weighted cache summaries), which is enough for an agent to know what it retrieves. It doesn't explicitly differentiate itself from siblings like get_cache_history or get_cache_summary, so it falls short of the top score.

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 guidance on when to use this tool rather than get_cache_history or get_cache_summary, nor any stated preconditions. The agent must infer usage from the name and the description's summary of contents.

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