Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

request_gym_enterprise

Ask the Trainzilla team for an enterprise plan for a gym (seats, phone, message). (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>",
      "input": "<input>"
    },
    "name": "request_gym_enterprise"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Only readOnlyHint=false is provided, and the description adds the valuable non-obvious detail that the tool is confirm-gated and previews until confirm: true. It does not say what actually happens on execution (e.g., a message to the Trainzilla team, expected response time), but the preview semantics are a real disclosure beyond the annotation.

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?

A single front-loaded sentence plus a short parenthetical caveat, with zero filler. The confirm-gate warning is placed where it will be seen before calling.

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 simple request/contact tool with no output schema, the description covers purpose, scoped fields, and execution semantics adequately. It stops short of saying what the caller receives back or what happens after submission, which would be the final missing piece.

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?

confirm and organizationId are documented in the schema, but the nested input object (phone, seats, message) has no field descriptions. The description merely names '(seats, phone, message)' without adding meaning or format, so it does not compensate for the remaining 33% coverage gap. Baseline 3 fits.

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: 'Ask the Trainzilla team for an enterprise plan for a gym', with the qualifying fields noted parenthetically. This is clearly distinguishable from subscription-mutation siblings such as change_organization_subscription_tier or cancel_organization_subscription — it is a request to sales, not a plan change.

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 by 'ask the team for an enterprise plan', but the description never states when to prefer it (e.g., when a gym needs enterprise terms rather than a listed seat tier) or what the alternative is. There are no explicit exclusions, so the agent must infer the trigger.

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