Skip to main content
Glama
Sign In

Gymmy

by com.hellogymmy
OverviewDiscussionsAdmin

Gym details

get_gym
Read-onlyIdempotent

Details of a gym: for a Gymmy gym its description, address, opening hours, sites, how to book, page and join links; for a gym not on Gymmy its address, opening hours, own booking link and sourced prices (with source and date, not verified by Gymmy), and its listing page.

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": {
      "gym": "<gym>"
    },
    "name": "get_gym"
  }
}

Input Schema

NameRequiredDescriptionDefault
gymYesGym identifier: the `gym` value from search_gyms (page slug or Gymmy id).
localeNoAnswer language: fr (default), en, pt, es or de. Pass en when the person writes in English.

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. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description does not need to restate safety. It does add genuine context beyond them: prices for non-Gymmy gyms are third-party sourced, carry a source and date, and are explicitly 'not verified by Gymmy' — a trust caveat an agent needs in order to present the data honestly.

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?

A single sentence with the two cases front-loaded and no filler, though the semicolon-chained enumeration of returned fields is dense and slightly hard to scan. Every clause is informative, so the density is earned rather than wasteful.

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?

There is no output schema, so the description must convey return contents — and it does, listing fields for both gym types plus the provenance caveat on prices. Only minor gaps remain, such as how the identifier is obtained (left to the schema) and any behavior when a gym is not found.

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 both parameters are already documented, including the enum of locales and the note to use en for English speakers. The description adds no meaning about either parameter (it never mentions locale or the identifier format), 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 (a gym) and enumerates exactly what is returned, split by the two meaningful cases: a Gymmy-listed gym (description, address, hours, sites, booking/how-to, page and join links) versus an off-platform gym (address, hours, own booking link, sourced prices, listing page). That is far more specific than 'get gym details' and implicitly separates it from search_gyms and join_gym.

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: the inclusion of 'sourced prices' shows this tool can also surface price data, but nothing states when to use this versus get_prices or join_gym, and no exclusion or prerequisite (e.g. needing an identifier from search_gyms) appears in the prose. The schema carries the identifier requirement, so the description adds no routing logic of its own.

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