Skip to main content
Glama

get_my_gym_checkin_code

Read-only

The staff member's own rotating check-in code for the gym (and when it expires), used by the front-desk/kiosk flow.

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

Input Schema

NameRequiredDescriptionDefault
organizationIdYesGym/organization _id (from list_my_organizations)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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, so the description is not carrying the safety burden. It still adds genuinely useful behavior the annotations do not cover: the code is rotating (so it must be re-fetched), it is scoped to the caller's own staff account, and an expiry is returned. It stops short of saying what happens if the code has expired or whether fetching invalidates a prior code.

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 sentence, front-loaded with the resource and its most decision-relevant property (rotation), followed by scope and use context. No filler or repetition of the title.

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-parameter read with no output schema, the description covers identity, scope, volatility, and return content well enough to call correctly. Only edge behavior (expired code, error cases) is left unspecified.

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?

There is a single required parameter and schema coverage is 100%, with the schema itself pointing to list_my_organizations as the source of the ID. The description adds no meaning about organizationId, so the baseline 3 applies.

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 a specific resource (the staff member's own rotating check-in code) and adds scope ('own') plus a returned attribute ('when it expires'), which separates it from siblings such as get_checkin or set_gym_face_checkin. It is clear without needing the schema, though it never states the retrieval verb outright.

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 phrase 'used by the front-desk/kiosk flow' implies the operational context, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. set_gym_face_checkin for enrolment vs. code display). Guidance is inferable rather than stated.

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.