Skip to main content
Glama

list_sessions

Read-only

List sessions — for one client (pass clientId) or all of the coach's clients.

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

Input Schema

NameRequiredDescriptionDefault
clientIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the default-scope behavior (no clientId means every client of the coach), but says nothing about result volume, ordering, or pagination for what could be a very large list.

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?

One short, front-loaded sentence with the zero-config default stated via the contrast between the two cases. Nothing is redundant or padded.

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 one-optional-parameter read-only list tool with annotations present and no output schema, the definition covers the essential decision (scope). The only meaningful omission is any hint about result size, ordering, or pagination, which matters for an unfiltered 'all clients' call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single property has no description, so the definition carries the full burden — and it does: it tells the agent that clientId selects a single client and that omitting it widens to all clients. That is exactly the semantic an agent needs to pick the right call.

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 gives a specific verb plus resource ('List sessions') and immediately scopes the resource to one client or the coach's whole roster, which tells an agent what domain 'sessions' means. It does not, however, disambiguate from siblings such as list_gym_class_sessions, so the bare word 'sessions' still requires inference.

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 explicitly states the two invocation modes: pass clientId for a single client, omit it to list all of the coach's clients. That is clear context for choosing the scope, but there are no negative conditions or named alternatives for cases like gym class sessions.

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.