Skip to main content
Glama

get_gym_attendance_summary

Read-only

Member attendance (booked / attended / no-show) and per-class fill rate over a date range.

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

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 safety is covered. The description adds the useful behavioral fact that output is aggregated (attendance counts plus a derived fill-rate metric) rather than raw records, but says nothing about scope boundaries, authorization needs, or how empty periods behave.

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 filler; the metric breakdown parenthetical sits right after the resource it qualifies. It earns its place, though the brevity is partly the cause of the missing parameter and return 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 read-only summary tool with no output schema and 0% schema coverage, the description covers the conceptual shape of the results but not their concrete structure or the date-window contract. It is adequate to pick the tool, but not quite enough to call it confidently.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must carry the semantics and largely does not. It implies a from/to window but never states the accepted date format, whether bounds are inclusive, or that organizationId scopes the query — all of which remain ambiguous for an agent constructing the 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 names the specific resource and metrics: member attendance broken out as booked / attended / no-show, plus per-class fill rate, over a date range. That is far more informative than the tool name alone and separates it from per-session siblings like get_gym_class_roster or mark_gym_class_attendance, though it never explicitly says whether it is a list or an aggregate report.

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 exclusions, and no pointer to an alternative. An agent must infer that this is the reporting tool and that roster/session tools are for per-member detail; nothing in the text states that trade-off.

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.