Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

assign_habit_to_groups

Give a reusable Master Habit (from master_habits) to every client in one or more groups. Members who already have a habit with that name are skipped. (confirm-gated: without confirm it previews who would get it, writing nothing)

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": {
      "masterHabitId": "<masterHabitId>",
      "groupIds": "<groupIds>"
    },
    "name": "assign_habit_to_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
groupIdsYesGroup ids from list_client_groups
masterHabitIdYes
allowDuplicatesNoAlso give it to a member who already has the same thing over the same dates (default: skip them)
excludeClientIdsNoMembers to leave out this time (client User _ids)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, so the description carries the important behavioral burden and does it well: it discloses the two-phase confirm/preview behavior and the skip-on-duplicate rule. It could go further on what the preview payload contains and whether allowDuplicates behaves over dates, but the core mutation semantics are disclosed.

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?

Three short sentences with zero filler: what it does, the dedupe rule, then the confirm gate. The most operationally important constraint (preview vs. write) is called out last in a parenthetical that is easy to scan.

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-ish bulk mutation with no output schema, the description covers the essential points an agent needs: the source of the habit, the group scoping, the skip rule, and the confirm gate. Only the shape of the preview response is left implicit, which is a minor gap given five parameters.

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 description coverage is 80%, so the schema already documents confirm, groupIds, allowDuplicates and excludeClientIds. The description reinforces the dedupe/skip behavior tied to allowDuplicates but adds little new on masterHabitId or excludeClientIds beyond what the schema states. Baseline 3 is appropriate here.

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 (Give), a specific resource (a reusable Master Habit from master_habits), and the distribution scope (every client in one or more groups). This clearly separates it from assign_master_habit (single client) and from assign_diet_to_groups/assign_workout_to_groups (different resource) without needing to open any schema.

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?

Explains the dedupe rule (members who already have a habit with that name are skipped) and the confirm-gating workflow (without confirm it previews, writing nothing), which tells an agent how to call it safely. It doesn't explicitly name assign_master_habit as the alternative for single-client assignment, so the routing guidance is clear but not exhaustive.

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 toolsInspect
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.

Resources