Trainzilla Coach MCP

delete_gym_face_template

Destructive

Delete one member's stored face template (e.g. on request). (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>",
      "userId": "<userId>"
    },
    "name": "delete_gym_face_template"
  }
}

Input Schema

Name	Required	Description
`userId`	Yes
`confirm`	No	Must be true to actually execute. If false/omitted, returns a preview only.
`organizationId`	Yes	Gym id (from list_my_organizations)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds genuinely new information: the operation is confirm-gated and returns a preview until confirm:true. It stops short of stating irreversibility, required permissions, or what happens when no template exists.

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 compact sentences with no waste, and the gating behavior is surfaced immediately after the core action. Nothing is padded or redundant.

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 3-parameter destructive tool with no output schema, the description covers the essential two-phase preview/confirm flow. Missing only edge-case details such as behavior when the user has no enrolled template or permission requirements.

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 67% and already documents confirm and organizationId; the description adds no parameter-level detail beyond the preview behavior. With moderate coverage, the schema does most of the work, so baseline 3 applies.

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 and resource ('Delete one member's stored face template'), which clearly distinguishes it from nearby siblings like get_gym_face_enrolments and set_gym_face_checkin. It doesn't explicitly name a sibling to avoid, so it stops just short of 5.

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?

The parenthetical '(e.g. on request)' implies the triggering situation (member-requested deletion) but gives no explicit when-not guidance or alternative tools. Usage context is implied rather than spelled out.

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 tools Inspect

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.