Skip to main content
Glama

get_gym_home

Read-only

Role-scoped gym overview: client and coach counts, this/last month revenue, new leads, today's classes, recent announcements, and billing state. Fields the coach's role can't see come back null.

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

Input Schema

NameRequiredDescriptionDefault
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's added value is the role-scoping disclosure: fields the coach's role cannot see come back null rather than raising an error. That is genuinely useful non-obvious behavior that prevents an agent from misreading nulls as missing data. It stops short of covering return shape, error cases, or whether the null set varies per caller.

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?

Two sentences, front-loaded with the tool's identity and scope before the return-field list and the null-behavior caveat. The field enumeration is dense but every item is a distinct returned datum, so nothing is padding.

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?

No output schema exists, so the description carries the return-value burden and does so by enumerating the returned sections and explaining the null-for-unpermitted-role case. What remains thin is the sole input parameter and any auth or organization-membership precondition, which an agent must guess at.

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?

The single parameter organizationId has 0% schema description coverage, so the schema provides no meaning at all. The description never mentions the parameter, its format, or how it interacts with the caller's role — the agent must rely on the self-describing name. With only one well-named required parameter this is a small gap, but the description does not compensate for the coverage deficit.

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 combination ('gym overview') and enumerates the exact contents: client/coach counts, this/last month revenue, new leads, today's classes, recent announcements, billing state. An agent can tell this is a dashboard-style read aggregate rather than the roster/attendance/record tools in the sibling list, though no sibling is named explicitly.

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 by the word 'overview' and the 'home' framing — an agent can infer it is the first-call summary endpoint. There is no explicit when-to-use guidance, no statement of when to prefer get_gym_attendance_summary or get_gym_member_record instead, and no mention of prerequisites such as authentication or role requirements.

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.