Skip to main content
Glama
Sign In
mcp-context-window

mcp-context-window

by donliggett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

context_list_sessions

Locate a session ID from earlier work by listing all stored sessions in reverse chronological order.

Instructions

List stored sessions, newest first. Use this to find a session id from earlier work when you do not remember it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

There are no annotations, so the description carries the behavioral burden. It discloses that the tool lists stored sessions in newest-first order and implies a read-only operation. This is adequate for a simple, parameter-free listing tool, though it does not explicitly state side effects or return format.

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 sentences with no fluff. The first states the action and ordering, the second gives a practical use case. Every sentence contributes meaningful information.

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

Completeness5/5

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

For a zero-parameter list tool, the description covers everything an agent needs: what it lists, the ordering, and why to call it. Nothing essential is missing because there is no complex schema, security concern, or ambiguity requiring further disclosure.

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 exposes zero parameters, so there is no parameter-level ambiguity to resolve. The description does not need to add parameter meaning because there are none, earning the baseline score for a tool with no parameters.

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?

The description clearly states the tool's action ('List stored sessions') and a distinguishing detail ('newest first'). It also names the concrete use case of finding a session id, making its purpose unambiguous and distinct from the doc_* siblings.

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?

It provides a specific scenario where the tool should be used: finding a session id from earlier work. It does not mention exclusions or alternatives, but the context is concrete enough for an agent to recognize when this listing tool is appropriate.

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

Deploy Server

Other Tools