Skip to main content
Glama

list_class_sessions

Read-onlyIdempotent

List class sessions and their capacity, booked spots and waitlist counts. Use Unix milliseconds and a window of up to 31 days. Use cancelled to filter by cancellation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "list_class_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
offsetNo
cancelledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the genuinely useful behavioral constraint that the time window cannot exceed 31 days, which the schema does not enforce. Pagination behavior via offset is not disclosed.

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?

Three short sentences, front-loaded with what the tool returns followed by the two operative constraints. No filler or restatement of the title.

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?

Without an output schema, the description usefully characterizes the returned values (capacity, booked spots, waitlist counts) and the time-window limit. It is silent on pagination, result ordering, and page-size limits, which matter for a list tool with an offset parameter.

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 coverage is 0%, so the description must carry the load; it documents 'from'/'to' as Unix milliseconds and constrains the window to 31 days, and explains that cancelled filters by cancellation. However, it leaves the offset parameter entirely undefined and does not clarify whether cancelled=true includes or excludes cancelled sessions or whether the window bounds are inclusive.

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 and resource ('List class sessions') and goes beyond the name by naming the data returned: capacity, booked spots, waitlist counts. It does not differentiate itself from siblings like get_class_session or list_class_roster, so an agent must infer that this tool is the multi-session listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives operating constraints (Unix milliseconds, a window of up to 31 days) which implicitly tells the agent when the tool is applicable. It offers no explicit routing guidance versus get_class_session or list_class_roster, and no stated exclusions.

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.

Resources