Skip to main content
Glama
Sign In

Gymmy

by com.hellogymmy
OverviewDiscussionsAdmin

Book a class

book_class

Books a class at one of the signed-in member's gyms with their own membership (or puts them on the waitlist when full, if the gym allows). Uses the gym's booking rules. No payment is taken here.

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": {
      "class_id": "<class_id>",
      "date": "<date>"
    },
    "name": "book_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
gymNoGym id (from my_schedule or my_gyms). Optional: found from the class when you belong to several gyms.
dateYesClass date (YYYY-MM-DD).
localeNoAnswer language: fr (default), en, pt, es or de. Pass en when the person writes in English.
class_idYesClass id (from my_schedule).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / locale / description
      Previous value: -"Answer language: fr (default) or en. Pass en when the person writes in English."New value: +"Answer language: fr (default), en, pt, es or de. Pass en when the person writes in English."
    • changedInput schema / properties / locale / enum
      Previous value: -[
-  "fr",
-  "en"
-]New value: +[
+  "fr",
+  "en",
+  "pt",
+  "es",
+  "de"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / locale / description
      Previous value: -"Answer language. Default fr."New value: +"Answer language: fr (default) or en. Pass en when the person writes in English."
  3. Changed1 schema field changed
    • changedInput schema / properties / gym / description
      Previous value: -"Gymmy gym id (from my_gyms). Needed only if you belong to several gyms."New value: +"Gym id (from my_schedule or my_gyms). Optional: found from the class when you belong to several gyms."
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write. The description adds real behavioral context on top: it may silently become a waitlist entry, it defers to each gym's booking rules, and it takes no payment. It does not say what happens if the class is full and no waitlist is permitted, or whether a booking consumes anything.

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 the action and immediately followed by the fallback and the payment disclaimer. Nothing is repeated from the schema or annotations, and every clause carries information an agent needs.

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 moderate write tool with full schema coverage and annotations, the definition covers action, scope, fallback, and pricing. The one remaining gap is the response shape: with no output schema, an agent cannot tell whether success returns a confirmed booking or a waitlist position, which matters given the waitlist branch.

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 100%, so all four parameters already carry their own documentation, including the optional gym id and the locale default. The description adds no extra meaning about date format, class id sourcing, or the locale effect, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Books a class" paired with a precise scope: at one of the signed-in member's gyms, using their own membership. The parenthetical waitlist behavior and the "No payment is taken here" clause separate it cleanly from book_dropin, which implies a paid drop-in booking.

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

Usage Guidelines4/5

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

The description establishes the condition for this tool (member booking against their own membership) and covers the full-class fallback (waitlist, if the gym allows). It stops short of explicitly naming the sibling to use instead when someone has no membership or wants a paid drop-in, so the routing is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gymmy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources