Trainzilla Coach MCP

assign_diet_to_groups

Give the same nutrition plan to every client in one or more groups (confirm-gated: without confirm it previews who would get it, writing nothing). Each client gets their own copy. Same meals format as create_diet_plan, including itemised ingredients on every meal. Note every member gets the same quantities, so for clients with very different calorie needs create individual plans instead. Undo with undo_group_assignment.

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": {
      "title": "<title>",
      "startDate": "<startDate>",
      "meals": "<meals>",
      "groupIds": "<groupIds>"
    },
    "name": "assign_diet_to_groups"
  }
}

Input Schema

Name	Required	Description
`meals`	Yes
`title`	Yes
`confirm`	No	Must be true to actually execute. If false/omitted, returns a preview only.
`endDate`	No
`groupIds`	Yes	Group ids from list_client_groups
`startDate`	Yes	YYYY-MM-DD
`allowDuplicates`	No	Also give it to a member who already has the same thing over the same dates (default: skip them)
`excludeClientIds`	No	Members to leave out this time (client User _ids)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does most of it: confirm-gating, write-nothing preview, per-client copy semantics, and the undo tool are all disclosed. It stops short of stating permission requirements, the 10-group cap (left to schema), or what the preview payload contains.

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?

Five sentences, zero padding, and the core action plus the confirm gate are front-loaded in sentence one. The caveat and undo path are placed after the happy path, which is the right order for an agent skimming before invocation.

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 an 8-parameter mutation tool with no annotations and no output schema, the description covers the dangerous parts: what gets written, when it doesn't write, and how to reverse it. Remaining gaps are the preview response shape and the group-count limit, both minor and partly covered by the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 63% schema coverage the description usefully adds meaning beyond the schema for the two most consequential inputs: the meals format is anchored to create_diet_plan with itemised ingredients, and confirm is framed as the execute/preview switch. excludeClientIds and allowDuplicates are left entirely to their schema text.

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+resource+scope: give the same nutrition plan to every client in one or more groups. It implicitly distinguishes itself from create_diet_plan (single client) and from the assign_habit_to_groups / assign_workout_to_groups siblings by naming the nutrition domain and the group-broadcast shape.

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

Usage Guidelines5/5

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

Explicitly names the when-not case ('clients with very different calorie needs → create individual plans instead') and the recovery path ('Undo with undo_group_assignment'). It also tells the agent that omitting confirm only previews, which is exactly the routing decision an agent must make before calling.

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.