Skip to main content
Glama
Sign In

Gymmy

by com.hellogymmy
OverviewDiscussionsAdmin

Start a trial class

start_trial
Read-onlyIdempotent

Gives the link to book a trial class at a Gymmy gym, with the trial offer and optionally the class already picked. The person opens it and confirms with their name and email; nothing is booked or charged by this tool.

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": "start_trial"
  }
}

Input Schema

NameRequiredDescriptionDefault
gymYesGym identifier: the `gym` value from search_gyms (page slug or Gymmy id).
dateNoClass date (YYYY-MM-DD).
localeNoAnswer language: fr (default), en, pt, es or de. Pass en when the person writes in English.
class_idNoClass id from get_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. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare the read-only/idempotent safety profile; the description adds real behavior beyond that — it returns a link rather than performing a booking, a human completes it with name and email, and no charge occurs. That closes the main ambiguity an agent would have about side effects.

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?

Two sentences, front-loaded with what the tool produces, followed by the follow-up step and the no-side-effect guarantee. No filler or redundant restatement of the name.

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 four-parameter tool with no output schema and clear annotations, the description covers the return (a link), the human handoff, and the absence of booking or charge. Minor gaps remain on link expiry/reuse and the date-versus-class_id relationship, which the schema also leaves open.

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% and each parameter is documented in the schema itself, so the baseline applies. The description adds only a little meaning: 'optionally the class already picked' clarifies that class_id is not required, but it says nothing about how date and class_id interact or about locale behavior.

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?

Specific verb and resource: it 'gives the link to book a trial class at a Gymmy gym'. The closing clause 'nothing is booked or charged by this tool' implicitly separates it from book_class/book_dropin, though no sibling is named explicitly.

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 implied rather than stated: an agent can infer this is the entry point for a trial signup and that the 'optionally the class already picked' case maps to passing class_id. There is no explicit 'use this instead of book_class when...' routing or stated prerequisite (e.g. gym must come from search_gyms).

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