Skip to main content
Glama

List Sessions

tm_operation_list_sessions
Read-onlyIdempotent

Lists active sessions and operations to track lifecycle and manage session state. Retrieve operation details for monitoring ongoing tasks.

Instructions

List sessions (tm_operations). Operation lifecycle and session management.

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

Input Schema

NameRequiredDescriptionDefault
confirmNoConfirm a destructive action (cancel) without elicitation.
detailsNoAdditional details (start).
total_stepsNoTotal steps (start).
operation_idNoOperation ID (get_progress/cancel/get_metrics).
operation_typeNoType of operation (start).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.4.7
    • addedInput schema / properties / confirm
      Added value: +{
      +  "default": false,
      +  "description": "Confirm a destructive action (cancel) without elicitation.",
      +  "type": "boolean"
      +}
  2. Addedv3.3.1

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context of its own, and notably does not explain why a read-only list tool carries a `confirm` parameter for "a destructive action (cancel)" or operation start fields. That mismatch is left entirely unaddressed.

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 short and front-loaded, which is good, but the second sentence is low-value jargon that does not help an agent decide or invoke. Brevity here is under-specification rather than efficiency.

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

Completeness2/5

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

For a tool with five parameters spanning start, progress, cancel, and metrics concerns, plus nested objects, the description should explain what is actually listed and why those parameters exist. An output schema exists so return values need no explanation, but the core operation scope 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?

Schema description coverage is 100%, so each parameter is already documented in the schema, which sets the baseline at 3. The description mentions no parameters at all, and does not clarify how start/cancel/get_metrics parameters relate to a listing operation.

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?

"List sessions" gives a verb and resource, but the parenthetical "(tm_operations)" and the follow-up "Operation lifecycle and session management" are vague taglines rather than a clear scope statement. It does not distinguish listing sessions from the sibling tools that start, cancel, or report progress on operations.

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 call this versus tm_operation_get_progress, tm_operation_cancel, or tm_operation_get_metrics, all of which appear as siblings. The agent must infer usage entirely from the name.

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