Skip to main content
Glama

list_gym_class_sessions

Read-only

Dated class sessions in a window, with bookings, waitlist and spots left. Defaults to the server's default window if from/to are omitted.

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": {
      "organizationId": "<organizationId>"
    },
    "name": "list_gym_class_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoISO date
fromNoISO date
locationIdNo
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds value beyond that: it discloses what the response contains (bookings, waitlist, spots left) and the default-window fallback when from/to are omitted. Pagination, ordering and result caps are not mentioned, keeping it below a 5.

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?

Two short sentences with no waste, and the resource-level scope is front-loaded ahead of the defaulting note. The opening is a noun fragment rather than a verb phrase, which slightly reduces immediate clarity about the operation.

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 four-parameter read tool with no output schema, the description covers the date window and response contents but leaves locationId and organizationId semantics unexplained and says nothing about ordering or result limits. 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 coverage is 50%: from/to are already documented as ISO dates in the schema, and the description only adds that together they define a window with a server default. locationId and the required organizationId receive no explanation in either place, so the description only partially compensates for the coverage gap.

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?

Names a specific resource (dated gym class sessions) and scope (a date window), plus what the result carries: bookings, waitlist and spots left. It does not explicitly distinguish itself from the ambiguous sibling list_sessions, so it falls short of a 5.

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?

Usage is only implied: the description says from/to form a window and that omitting them falls back to the server's default window. There is no statement of when to prefer this over list_sessions or list_gym_class_standings, and no prerequisites or 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.