Skip to main content
Glama
Sign In

Gymmy

by com.hellogymmy
OverviewDiscussionsAdmin

Prices and offers

get_prices
Read-onlyIdempotent

Memberships, class packs and trial offers of a Gymmy gym with prices in EUR and a direct sign-up link per offer.

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

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: prices are denominated in EUR regardless of locale, and each offer carries a direct sign-up link. It does not say what happens for a gym with no offers or an unknown gym id.

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 front-loaded sentence with zero filler; the content-bearing terms (offer types, EUR prices, sign-up link) come early. It reads as a fragment rather than a complete statement of action, which slightly weakens selection speed.

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

Completeness3/5

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

For a simple two-parameter read tool with no output schema, the description does a fair job listing what is returned, which is the main thing an agent needs. It is still thin on edge cases (gym without offers, invalid id) and on where this tool sits in the flow toward start_trial.

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%, including a documented enum for locale with a stated default, so the schema carries the parameter burden. The description contributes no additional meaning about the `gym` identifier or how locale interacts with the fixed EUR currency, which is the one interaction worth flagging.

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 the concrete resource set — memberships, class packs and trial offers with prices and sign-up links for a specific gym — so an agent knows exactly what comes back. It stops short of differentiating itself from siblings such as get_gym or start_trial, and is phrased as a noun phrase rather than an explicit retrieve verb.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no prerequisite (e.g. obtain the gym id from search_gyms), and no routing to alternatives like get_gym for general gym details or start_trial for acting on an offer. Usage is only inferable from the returned-content list.

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