Skip to main content
Glama

assign_workout_to_groups

Give the same workout 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, so it can be edited per person afterwards. Members who already have a plan with this title over overlapping dates are skipped. Same exercises format as create_workout_plan (call get_training_split first and use search_exercises ids). 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>",
      "exercises": "<exercises>",
      "groupIds": "<groupIds>"
    },
    "name": "assign_workout_to_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
titleYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
endDateNo
groupIdsYesGroup ids from list_client_groups
exercisesYes
startDateYesYYYY-MM-DD
descriptionNo
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.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the preview-vs-write confirm gate, per-client copy behavior, duplicate-skipping default, and undo path. These are precisely the mutation behaviors an agent needs before invoking the tool.

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 front-loaded with the core action, then layers in confirm behavior, copy semantics, duplicate handling, prerequisite format, and undo. Every sentence is functional and there is no filler.

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 10-parameter mutation tool with no annotations and no output schema, the description covers the essential behavior: preview, execution, duplicate skipping, per-client copies, exercise format prerequisites, and undo. Some lower-level parameters remain schema-only, but the definition is otherwise complete enough to call the tool correctly.

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?

Schema coverage is 50%, and the description adds important meaning for key parameters: confirm controls preview versus execution, allowDuplicates overrides the overlap skip, and exercises must follow create_workout_plan format using search_exercises ids. It does not explain every parameter, such as excludeClientIds, days, or endDate, but it compensates for the most consequential ones.

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?

The description states a specific verb and resource: give the same workout plan to every client in one or more groups. It distinguishes the tool from single-client plan creation by emphasizing bulk group assignment, and it names related tools such as create_workout_plan, get_training_split, search_exercises, and undo_group_assignment.

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?

It explicitly explains the confirm-gated workflow: without confirm it previews and writes nothing. It gives the prerequisite workflow (call get_training_split first and use search_exercises ids), describes skip behavior for overlapping plans, and names undo_group_assignment as the reversal path.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.