Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

set_gym_face_checkin

Turn face check-in on/off for a gym. Turning on requires attest: true (the gym confirms it has members' consent). (confirm-gated: previews until confirm: true)

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": {
      "organizationId": "<organizationId>",
      "enabled": "<enabled>",
      "attest": "<attest>"
    },
    "name": "set_gym_face_checkin"
  }
}

Input Schema

NameRequiredDescriptionDefault
attestYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
enabledYes
organizationIdYesGym id (from list_my_organizations)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only give readOnlyHint=false; the description adds real value by explaining the consent/attestation prerequisite for enabling and the preview-until-confirm semantics of the call. It does not explain what happens to existing face enrolments when disabling, which is the one meaningful behavioral gap for a toggle.

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 the action, then the prerequisite, then the gating caveat in parentheses. Nothing is padded and the conditional requirement is placed right where an agent would look for it.

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 4-param mutation with no output schema and only a readOnlyHint, the description covers the enable path well but is silent on the disable path — whether turning off wipes enrolled face templates, and what the response contains. Adequate to call correctly, but not fully complete for a state-changing toggle.

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?

With 50% schema coverage, the description compensates by explaining the two undocumented parameters: it ties 'attest' to the consent confirmation and implicitly scopes 'enabled' to turning the feature on/off. The confirm behavior is restated from the schema's own description, so it earns no extra credit there.

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?

States a specific verb ('turn on/off') and a specific resource ('face check-in for a gym'), which no sibling duplicates — the closest siblings (get_gym_face_enrolments, delete_gym_face_template) are clearly reads/deletes. It doesn't explicitly contrast with those siblings, but an agent can identify the correct tool from the description alone.

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 context is implied rather than stated: the agent learns that enabling requires attest and that the call is confirm-gated, but there is no explicit 'use this when…' or 'do not use for…' guidance. Since no sibling competes for this exact action, the omission is minor rather than harmful.

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

All Trainzilla Coach MCP 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