Skip to main content
Glama
Sign In
Loom

Loom

by MlkBlk-IT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Ctx List Sessions

ctx_list_sessions
Read-onlyIdempotent

Lists stored Loom sessions with metadata and stats, and optionally includes expired sessions past their TTL for review.

Instructions

List all sessions with metadata and stats.

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

Input Schema

NameRequiredDescriptionDefault
include_expiredNoif true, include sessions past their TTL (default: false)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, closed-world behavior, so safety is covered. The description adds only that each entry carries metadata and stats, but says nothing about pagination, volume, ordering, or how expired sessions are treated beyond the schema's default.

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?

A single front-loaded sentence with zero waste. It is appropriately sized, though correspondingly it carries little detail.

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 simple one-optional-parameter listing tool with an output schema and rich annotations, the description covers the core purpose but omits usage context and any hint of return shape or scale. Adequate but with clear gaps.

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?

Schema description coverage is 100%, so include_expired is fully documented in the schema. The description adds no extra meaning about parameter effects (e.g., whether expired sessions appear in counts), so the baseline 3 applies.

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 states a specific verb (List) and resource (sessions) plus the payload (metadata and stats), which lets an agent distinguish it from ctx_get (single session retrieval) and ctx_stats (aggregate stats). It stops short of explicitly naming any sibling as an alternative.

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 alternatives such as ctx_get or ctx_stats, and no exclusions. The agent must infer from the name alone that this is the enumeration entry point.

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