Skip to main content
Glama

generate_ai_meal_plan

Destructive
Fill an AI meal plan from its saved answers, or refill it, replacing
every meal not marked kept (keep_meal_plan_entry) -- requires
Subscriber. Takes up to a minute and counts against the account's
daily generation limit. Returns the plan, including `summary`:
per-day nutrition against the household's goals, the week's cost, and
any meals it couldn't fill.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "generate_ai_meal_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesA meal plan's id: `plans[].id` from list_meal_plans, or `id` from create_ai_meal_plan.
session_tokenNoThe session token check_agent_connection returned for the connected account. Required, unless it's sent as an Authorization: Bearer header on the MCP request instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description earns real credit on top: it says exactly what is destroyed (every meal not marked kept), names the auth requirement (Subscriber), discloses latency (up to a minute) and a rate limit (counts against the daily generation limit). It also describes the returned payload, which matters because there is no output schema.

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 dense clauses, front-loaded with what the tool does and what it overwrites, then prerequisites, then cost and return shape. No filler sentences and nothing repeated from the schema.

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 destructive, slow, rate-limited mutation with no output schema, the description covers the destruction semantics, the auth requirement, timing, quota consumption, and the return shape including the summary breakdown. An agent has everything needed to decide and to set expectations.

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 100%, so both plan_id and session_token are already well documented in the schema. The description adds only an indirect hint that the referenced plan must already carry saved answers; it adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 (fill/refill) on a specific resource (an AI meal plan) and scopes it: it rebuilds from saved answers, replacing every meal not marked kept. That scope plus the parenthetical cross-reference to keep_meal_plan_entry cleanly separates it from create_ai_meal_plan and the entry-level tools.

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?

It gives clear triggering context (plan already has saved answers; fill or refill), states the Subscriber prerequisite, and points at keep_meal_plan_entry as the way to protect meals from replacement. What's missing is an explicit comparison with create_ai_meal_plan for an agent starting from a plan that has no saved answers yet.

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.

Resources