Phorme Training

Find a Phorme gym or class

find_gym_class

Read-only

Use this when the user wants a gym, studio or class to train at in person, for example "a strength class in Austin this week" or "a gym near me". It returns up to five Phorme gyms, studios and other places to train in the city named or, when no city is named, within 60 km (or radius_km) of the approximate location the assistant shares, nearest or best matching first, each with its page on phor.me and its classes in the coming days with the class id, local start time, length, places left and a link to book on phor.me. When nothing matches it returns alternatives: the nearest places further out, and a home plan from a Phorme coaching brain. It reads only and shows no prices; booking a class for a signed-in user is a separate step.

Input Schema

Name	Required	Description
`city`	No	The city the user named, for example "Austin".
`days`	No	How many days ahead to look. Default 7.
`radius_km`	No	How far to look, in km. Default 60. Use a larger one only when the user said they would travel.
`class_type`	No	The kind of class, only if the user said, for example "barbell" or "yoga".

Output Schema

Name	Required	Description
`limits`	Yes	What this does not cover. Tell the user.
`places`	Yes	Gyms, studios and other places to train, nearest or best matching first: place_id, name, kind, line, city, country, distance_km, page_url and classes (class_id, the id book_gym_class takes, then title, line, starts, minutes, spots_left, book_url).
`alternatives`	No	When nothing matched or no class is scheduled: kind (wider_radius, other_cities, home_plan), line (what to offer), tool, and for wider_radius the nearest places further out. Offer them; never leave the user with nothing.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 25, 2026

removedInput schema / properties / near_lat

Removed value: -{
-  "description": "Latitude, only if the user shared their position.",
-  "maximum": 90,
-  "minimum": -90,
-  "type": "number"
-}

removedInput schema / properties / near_lon

Removed value: -{
-  "description": "Longitude, only if the user shared their position.",
-  "maximum": 180,
-  "minimum": -180,
-  "type": "number"
-}

changedInput schema / properties / radius_km / description

Previous value: -"How far from the shared position to look, in km. Default 60. Use a larger one only when the user said they would travel."New value: +"How far to look, in km. Default 60. Use a larger one only when the user said they would travel."

Changed3 schema fields changedOct 19, 2026

addedInput schema / properties / radius_km

Added value: +{
+  "description": "How far from the shared position to look, in km. Default 60. Use a larger one only when the user said they would travel.",
+  "maximum": 300,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / alternatives

Added value: +{
+  "description": "When nothing matched or no class is scheduled: kind (wider_radius, other_cities, home_plan), line (what to offer), tool, and for wider_radius the nearest places further out. Offer them; never leave the user with nothing.",
+  "type": "array"
+}

changedOutput schema / properties / places / description

Previous value: -"Gyms and studios, nearest or best matching first: name, kind, line, city, country, distance_km, page_url and classes (title, line, starts, minutes, spots_left, book_url)."New value: +"Gyms, studios and other places to train, nearest or best matching first: place_id, name, kind, line, city, country, distance_km, page_url and classes (class_id, the id book_gym_class takes, then title, line, starts, minutes, spots_left, book_url)."

AddedOct 14, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Despite annotations already covering the read-only safety profile, the description adds substantial behaviour: a cap of five results, nearest-or-best-match ordering, the per-result payload (page link, class id, local start time, length, places left, booking link), the no-match fallback to further-out places plus a coaching-brain home plan, and the explicit note that no prices are shown. These are traits an agent could not infer from the annotations.

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?

Front-loaded correctly with the trigger sentence before the return-value detail, and no filler. It is one long run-on paragraph however, and the return-format middle clause could be split for easier scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, zero-required search tool with an output schema, this covers everything an agent needs: when to call it, how location resolution works, result ordering and count, what each result contains, and what happens on empty results. Return-value detail is redundant with the output schema but harmless.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: city being optional and falling back to a 60 km (or radius_km) search around a shared location, and that it looks at classes "in the coming days" matching the days parameter. Only class_type and the exact days default are left to the schema, so it improves on baseline without being exhaustive.

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?

States a specific verb and resource (find gyms, studios and classes to train at in person) and immediately scopes it to the in-person training case with concrete example queries. An agent can distinguish this from find_clinic, find_personal_coach, find_races or book_gym_class without inspecting any schema.

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

Usage Guidelines5/5

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

Opens with an explicit trigger ("Use this when the user wants a gym, studio or class to train at in person") that matches sibling tools' territory. It also draws the boundary against the booking flow ("booking a class for a signed-in user is a separate step"), routing that need to book_gym_class, and explains the fallback when no city is named.

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

All Phorme Training 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.