Trainzilla Coach MCP

remove_gym_custom_domain

Destructive

Disconnect a gym's custom domain. (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>"
    },
    "name": "remove_gym_custom_domain"
  }
}

Input Schema

Name	Required	Description	Default
`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 only supply destructiveHint=true; the description adds genuinely new behavior — the call is confirm-gated and returns a preview unless confirm:true is passed. That is exactly the kind of non-obvious trait an agent needs. It still omits what actually happens on execution (DNS/SSL teardown, whether the domain is released) and permission requirements, so it is not a 5.

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 short clauses, no waste, and the core action is front-loaded ahead of the parenthetical behavior note. Nothing to trim.

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 two-parameter mutation with full schema coverage and destructiveHint, the description covers the essentials including the two-phase preview/execute flow. It lacks post-removal consequences and required permissions, which would matter for a destructive org-level operation, but the gaps are modest.

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%, so both parameters are already fully documented, including the confirm semantics and the organizationId source (list_my_organizations). The description restates the confirm gating rather than adding new parameter meaning. 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: "Disconnect a gym's custom domain." The word "gym" implies organization-scoped operation, which separates it from remove_my_custom_domain in the sibling list, but that distinction is never made explicit. An agent can tell what the tool does, just not fully why it differs from the near-identical sibling.

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 the name and the confirm-gating note, but the description never says when to prefer this over remove_my_custom_domain or the connect/refresh siblings. There are no exclusions or prerequisites (e.g. domain must be connected, org admin required).

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.