Skip to main content
Glama

list_meal_plans

Read-only
The connected account's meal plans -- requires Subscriber. Returns
`plans` (each with `id`, `kind` "manual" or "ai", `name`, and
`generated_at` for an AI plan), plus `limits` and `counts`: an
account has at most one hand-built plan and five AI plans. Pass a
plan's `id` to get_meal_plan_details for its meals.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_meal_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral facts: a Subscriber entitlement gate and account quotas (at most one hand-built plan and five AI plans), which tell the agent what to expect for `limits` and `counts`. It doesn't discuss failure modes for non-subscribers, which keeps it at 4.

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 sentences, front-loaded with the resource and entitlement, then the return shape, then the next-step pointer. The field-by-field return enumeration is somewhat dense but justified because there is no output schema. No filler text.

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?

With no output schema, the description correctly compensates by naming the returned keys and the meaning of `kind` values, plus quota semantics. Entitlement requirement and the hand-off to a sibling tool are both covered. The only residual gap is how this listing relates to the similarly named `get_my_meal_plan`.

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?

There is one parameter and schema description coverage is 100%, with the schema fully explaining `session_token` and its Authorization-header alternative. The description says nothing about the parameter, so baseline 3 applies — the schema carries the full load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific resource and scope: the connected account's meal plans, with an entitlement note (requires Subscriber). It doesn't literally use the verb 'list', but the enumeration of `plans`, `limits`, and `counts` makes the read-and-return behavior unambiguous. It partially differentiates from `get_meal_plan_details` by deferring per-meal detail to that tool.

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 states a prerequisite ('requires Subscriber') and explicitly routes the agent onward: 'Pass a plan's `id` to get_meal_plan_details for its meals.' That is a clear use-vs-alternative signal. It doesn't address when to prefer this over `get_my_meal_plan` or `get_meal_plan_details` more broadly, so it stops short of full when/when-not coverage.

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