Trainzilla Coach MCP

delete_gym_announcement

Destructive

Delete a gym announcement. (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>",
      "announcementId": "<announcementId>"
    },
    "name": "delete_gym_announcement"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be true to actually execute. If false/omitted, returns a preview only.
`announcementId`	Yes
`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?

The destructiveHint annotation already flags this as a destructive operation, and the description adds useful safety context by explaining the confirm-gated preview behavior. It does not mention permissions, irreversibility, or side effects beyond deletion.

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?

The description is two short sentences with no wasted words, and the core action is front-loaded before the confirmation behavior. It is appropriately sized for this tool.

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 destructive delete tool with a destructiveHint annotation and no output schema, the description covers the key safety behavior through the confirm-gated preview. It could be more complete by mentioning permissions or irreversibility, but the essential invocation context is present.

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%, with organizationId documented and confirm documented in the schema. The description reinforces the confirm gate but adds no new meaning for announcementId or other parameter semantics beyond what the schema already provides.

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 states a specific verb and resource: "Delete a gym announcement." This clearly distinguishes it from sibling tools like list_organization_announcements and send_organization_announcement, though it does not explicitly name alternatives.

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 description indicates the confirmation workflow: it previews until confirm is true. However, it does not explicitly compare this tool to alternatives such as listing or sending announcements, nor does it state when deletion is appropriate versus other actions.

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.