Trainzilla Coach MCP

create_client_portal_link

Create a private no-login link for a client (check-ins, plans, receipts, sessions) to send over WhatsApp. The URL is shown once. (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": {
      "clientId": "<clientId>"
    },
    "name": "create_client_portal_link"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be true to actually execute. If false/omitted, returns a preview only.
`clientId`	Yes	Client's User _id (from list_clients)
`expiresInDays`	No

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 annotations only provide readOnlyHint=false; the description adds important behavior beyond that: the link is private and no-login, the URL is shown once, and the operation previews until confirm=true. It does not cover permissions, expiry semantics, or what happens to previously issued links, which keeps it from 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 tight sentences plus a parenthetical, with the core action, one-time URL behavior, and confirm gate front-loaded. Nothing is wasted or redundant with 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-parameter mutation with no output schema, the description covers what is created, how the URL is delivered, and the preview-before-execute behavior. It leaves expiry semantics and response details implicit, but the main context needed to invoke it correctly 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%, and confirm/clientId already have schema descriptions. The description reinforces confirm gating but does not explain expiresInDays, which lacks a schema description, nor does it clarify expiry defaults or effects beyond the schema.

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: create a private no-login client portal link, including the content types it exposes. It distinguishes itself from generic invite or plan-share links by emphasizing no-login client portal access, but it does not explicitly name sibling 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?

Gives intended usage context (send over WhatsApp) and notes the confirm-gated preview behavior. However, it does not state when to use this instead of related tools such as create_invite_link, create_plan_share_link, or revoke_client_portal_links, so routing guidance is implied rather than explicit.

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.