Skip to main content
Glama

update_group_workout_assignment

Change a workout that was given to groups (assignmentId from list_group_assignments): title, description, exercises, days or dates, applied to each member's copy that the coach has not edited themselves. Confirm-gated: without confirm it previews which members would change and which would be skipped. Exercises use the same format as create_workout_plan.

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": {
      "assignmentId": "<assignmentId>"
    },
    "name": "update_group_workout_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
titleNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
endDateNo
exercisesNo
startDateNoYYYY-MM-DD
descriptionNo
assignmentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (which only declare it non-read-only, non-destructive, closed-world), the description discloses the confirm-gating contract, that a call may be a preview rather than a mutation, that changes propagate per-member, and that some members are skipped entirely. Those are exactly the behaviors an agent must know before invoking a fan-out mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and front-loaded, with the target resource first and the confirm-gating caveat immediately after. The single long sentence with chained parentheticals is slightly run-on but carries no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With eight parameters, no output schema, and thin schema descriptions, the definition still covers what the agent needs: identifier source, mutation scope, preview-vs-execute switch, partial-application semantics, and the exercise payload format. No material gap remains for correct invocation.

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 only 25%, so the description must compensate, and it largely does: it explains assignmentId's provenance, the confirm semantics (matching the schema's own description), the day/date fields, and points to create_workout_plan for the exercises format. It adds little about startDate's YYYY-MM-DD expectation, but the schema already covers that one field.

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 and resource ("Change a workout that was given to groups"), enumerates the mutable fields (title, description, exercises, days/dates), and ties the required assignmentId to its source tool, list_group_assignments. This distinguishes it cleanly from siblings like update_workout_plan or assign_workout_to_groups.

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?

Gives concrete usage context: fetch assignmentId from list_group_assignments, and note that without confirm the call only previews. It also flags the exclusion rule that members whose copies the coach edited are skipped. It stops short of explicitly contrasting against sibling update tools for the non-group case.

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.