Skip to main content
Glama

get_my_meal_plan

Read-only
The connected account's hand-built 7-day meal plan (Monday-Sunday x
Breakfast/Lunch/Dinner/Snacks) -- requires Subscriber. For AI plans,
use list_meal_plans and get_meal_plan_details instead. Each slot's
entries carry an `entry_id` and their recipe's own nutrition fields.
Daily/weekly totals are NOT pre-summed here -- sum the real
per-recipe numbers yourself if a calorie target matters (e.g. "stay
under 2000 calories a day"); never estimate or round a total you
weren't actually given.

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": "get_my_meal_plan"
  }
}

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

A4.3/5.0
Behavior4/5

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

Annotations only cover readOnly/openWorld, and the description adds real behavioral context: the Subscriber entitlement requirement, that each slot entry carries an entry_id plus the recipe's own nutrition fields, and an explicit instruction not to estimate or round totals. It stops short of saying what an empty/unset plan returns or how totals-related errors surface.

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?

Front-loaded with the resource definition and the exclusion rule, then the data-shape note, then the totals caveat. Every sentence carries information, though the backtick/line-break formatting is a bit noisy for prose.

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 does the heavy lifting on return shape (entry_id, per-recipe nutrition) and warns against fabricating sums, which is the key failure mode for calorie-target questions. Missing only edge-case behavior (no plan configured, non-subscriber response) and pagination/limit 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?

Single parameter at 100% schema description coverage — the schema already explains session_token and its Authorization-header alternative. The description adds nothing about it, so 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 resource and its exact shape: the connected account's hand-built 7-day meal plan, Monday–Sunday × Breakfast/Lunch/Dinner/Snacks. It explicitly distinguishes this from the AI-plan siblings (list_meal_plans / get_meal_plan_details), so an agent can pick it without opening another schema.

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?

Gives an explicit when-to-use (hand-built plan) and when-not-to-use (for AI plans, call list_meal_plans then get_meal_plan_details), naming the alternatives directly. It also surfaces a prerequisite — requires Subscriber — that gates the call.

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