Gymmy

Find a class to drop in

search_classes

Read-onlyIdempotent

Classes open to visitors right now at Gymmy gyms that accept drop-ins from anywhere (trial, single class or class pack), near a place or point, optionally one day or one kind of class ('hyrox', 'yoga'). Each result has the gym, class_id, date, spots left, the cheapest price and the offers that book it (offer_id). Book one with book_dropin.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_classes"
  }
}

Input Schema

Name	Required	Description
`gym`	No	Only this gym (Gymmy id from search_gyms).
`lat`	No	Latitude to search around.
`lng`	No	Longitude to search around.
`date`	No	Only this day (YYYY-MM-DD).
`class`	No	Kind of class or coach to match, e.g. 'WOD', 'HYROX', 'Yoga'.
`limit`	No	Max results. Default 15.
`query`	No	Place to search around: address, district, city or postcode ('Lyon 7', 'Bastille'). Geocoded when no lat/lng is given.
`locale`	No	Answer language: fr (default), en, pt, es or de. Pass en when the person writes in English.
`radius_km`	No	Radius in km, 1 to 50. Default 15, or fitted to the place.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

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"
+]

Changed1 schema field changedNov 9, 2026

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."

AddedOct 24, 2026

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 read-only, idempotent, non-destructive search. The description adds meaningful behavior beyond that: it defines eligibility (visitors, drop-in acceptance, trial/single/pack offers) and lists the key result fields, which is especially useful because there is no output schema. It stops short of covering ordering, pagination, or empty-result behavior.

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?

The description is front-loaded with the purpose, then summarizes result contents, then names the booking handoff. Every sentence contributes useful information and there is no filler.

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 nine-parameter search tool with no output schema, the description does a good job explaining eligibility and what each result contains, while the schema handles parameter details. It is not fully complete because it omits result ordering, pagination, and behavior when no classes match.

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 description coverage is 100%, so all nine parameters are already documented. The description adds only conceptual framing around searching near a place or point and optionally filtering by day or class kind; it does not add syntax or constraints beyond the schema.

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?

The description gives a specific verb and resource: classes open to visitors at Gymmy gyms that accept drop-ins, searchable near a place or point with optional date or class-kind filters. It also names book_dropin as the follow-up action, so an agent can distinguish this search tool from the booking sibling without opening the schema.

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?

It clearly frames the use case as finding a drop-in class to book and explicitly routes the next action to book_dropin. It does not explicitly say when to use it instead of get_schedule or search_gyms, so there is still a small gap in alternative selection guidance.

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

All Gymmy tools Inspect

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.