Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

get_gym_imported_sales_summary

Read-only

Totals of imported sales per currency and per month.

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>"
    },
    "name": "get_gym_imported_sales_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationIdYesGym id (from list_my_organizations)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the description only needs to add context. It adds the aggregation shape (per currency, per month), but says nothing about time-window behavior (all-time vs range), what happens when no imported sales exist, or whether uncommitted imports count.

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?

One short, front-loaded sentence with zero filler. It is a noun phrase rather than a statement of action, which is slightly less scannable than a verb-first sentence.

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?

With no output schema, the description must carry the return semantics; it partially does by naming the grouping dimensions, but omits the shape of each row (count, amount, currency code), date window, and ordering.

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?

Single parameter with 100% schema coverage, and the schema already explains organizationId sources from list_my_organizations. The description adds no additional meaning, which is acceptable at full coverage but earns only the baseline.

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 resource (imported sales) and the exact aggregation axes (totals per currency per month), which is more specific than a restatement of the name. It never names the obvious sibling list_gym_imported_sales, so differentiation from the raw-list tool is left to inference.

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 mention of prerequisites (e.g. an import must exist or be committed), and no routing to list_gym_imported_sales for row-level data. An agent must guess whether this is for reconciliation, dashboards, or reporting.

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