Skip to main content
Glama
Tandoor Recipes MCP

Tandoor Recipes MCP

List meal plans

list_meal_plans
Read-onlyIdempotent

Retrieve meal plans created by you or your household and filter by date range to review or manage past and upcoming meal schedules.

Instructions

List meal plans made by you or your household. Optional: from_date, to_date (YYYY-MM-DD, matched on the end date of each entry; default 90 days ago to 360 days ahead).

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
pageNoPage number, starting at 1.
to_dateNoRange end, YYYY-MM-DD. Default 360 days ahead.
from_dateNoRange start, YYYY-MM-DD. Default 90 days ago.
page_sizeNoResults per page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.4.4
    • addedInput schema / properties / from_date / description
      Added value: +"Range start, YYYY-MM-DD. Default 90 days ago."
    • addedInput schema / properties / page / description
      Added value: +"Page number, starting at 1."
    • addedInput schema / properties / page_size / description
      Added value: +"Results per page."
    • addedInput schema / properties / to_date / description
      Added value: +"Range end, YYYY-MM-DD. Default 360 days ahead."
  2. First observedv3.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: the default window (90 days back to 360 days ahead) and, more valuably, that the date filter matches on the END date of each entry rather than the start. It does not mention result ordering or pagination behavior, which keeps it below a 5.

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?

Two sentences, no filler, with the core purpose front-loaded and the optional parameter semantics grouped into a single trailing clause. Nothing is repeated from the title and nothing is wasted.

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?

For a four-parameter, all-optional listing tool with full schema coverage and no output schema, this covers what an agent needs to call it correctly. The remaining gap is minor: no indication of result ordering or how pagination interacts with the date window.

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 100%, so the baseline would be 3. The description earns a point above that by clarifying that from_date/to_date are matched against each entry's end date, a semantic detail absent from the schema, and by restating the defaults compactly. It is silent on page/page_size, but those are self-documented in the schema.

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?

States a specific verb and resource ('List meal plans') and adds a scope qualifier ('made by you or your household'). The plural/listing nature distinguishes it implicitly from the singular get_meal_plan, though the description never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: it is a listing tool with an optional date window, so an agent can infer when to reach for it. There is no explicit 'use this instead of X when...' guidance and no note about when a date window is required or inadvisable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.