Skip to main content
Glama

update_group_diet_assignment

Change a nutrition plan that was given to groups (assignmentId from list_group_assignments): title, description, meals 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. Meals use the same format as create_diet_plan, including itemised ingredients.

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_diet_assignment"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing cascade semantics (changes propagate to each member's copy), the exemption rule (members whose copy the coach edited are skipped), and the preview-only behavior when confirm is false. The only tension is that destructiveHint=false understates a bulk overwrite of member plans, though the skip rule and preview gate make the description itself non-contradictory.

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?

Three dense sentences with the resource and scope first, the targeting rule next, and the confirm gate last. Every sentence carries information; the only mild inefficiency is folding meal-format guidance into the same block rather than separating it.

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?

For a multi-target mutation with 7 parameters and no output schema, the description covers the identity source, the affected scope, the skip rule, and the two-phase preview/execute flow. An agent has everything needed to call it safely without further documentation.

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 29%, so the description carries real weight and does: it enumerates the updatable fields (title, description, meals, dates), explains confirm's preview semantics, gives the assignmentId source, and points to create_diet_plan's meal format including itemised ingredients. Date format and per-field constraints are left to the schema, but the conceptual meaning of every parameter is covered.

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 nutrition plan that was given to groups') and names the fields it can modify, and it identifies the required key's origin ('assignmentId from list_group_assignments'). The group-scoped framing plus the 'applied to each member's copy' clause distinguishes it clearly from the individual-plan siblings like update_diet_plan.

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?

Tells the agent where to obtain assignmentId (list_group_assignments) and explains the confirm-gated workflow: without confirm it previews which members change and which are skipped. It does not explicitly say when to prefer update_diet_plan or assign_diet_to_groups instead, so the alternative routing is only implied.

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.