Trainzilla Coach MCP

pin_community_post

Pin or unpin a post at the top of the community (moderators). (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": {
      "postId": "<postId>",
      "pinned": "<pinned>"
    },
    "name": "pin_community_post"
  }
}

Input Schema

Name	Required	Description
`pinned`	Yes
`postId`	Yes
`confirm`	No	Must be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only say readOnlyHint=false; the description adds valuable beyond-annotation detail: moderator-only authorization and that calls preview rather than execute until confirm:true. It omits what happens to a previously pinned post or whether unpinning is reversible.

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 clauses, action first, then the execution gate and role qualifier. No filler and the critical confirm gate is visible without opening the schema.

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-param mutation with no output schema, the description covers authorization, the two-step confirm workflow, and the effect (pinning to top). Minor gaps remain around return payload and pin uniqueness, but nothing blocking correct invocation.

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 only 33%, so the description must compensate. It explains the semantics of 'confirm' (preview vs execute) and maps implicitly to the pinned boolean via 'pin or unpin', but leaves postId format and the single-pin-vs-multiple-pin behavior unexplained.

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 pair (pin/unpin), the exact resource (a post at the top of the community), and the toggle semantics via the single tool. An agent can immediately tell this apart from create_community_post, delete_community_post, and react_to_community_post.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Adds the permission context '(moderators)' and explains the confirm-gated two-step invoke pattern, which is real usage guidance. It does not name explicit alternatives or when-not conditions, keeping it below a 5.

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.