plan-to-eat-mcp

get_planner_week

Retrieve meal planner events within a specified date range, defaulting to a week, and include corresponding recipe titles for easy planning.

Instructions

Fetch all planner events between start_date and end_date (inclusive, YYYY-MM-DD). end_date defaults to start_date + 6 days. Recipe events are enriched with recipe_title.

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": {
      "start_date": "<start_date>"
    },
    "name": "get_planner_week"
  }
}

Input Schema

Name	Required	Description	Default
`end_date`	No
`start_date`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Sep 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description discloses read-only behavior ('Fetch'), the default date logic, and the enrichment of recipe events with `recipe_title`. It does not mention error handling or pagination, but provides key behavioral details.

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 deliver all necessary information with no redundancy, efficiently covering functionality and parameter behavior.

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?

The description implies a return of planner events and notes the `recipe_title` enrichment, which is sufficient for basic understanding. It omits return shape and edge cases, but given the simplicity, it's reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters (`start_date`, `end_date`) are explained with format and the default for `end_date` is given. This fully covers their semantic meaning beyond the schema's pattern constraint.

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?

The description clearly states the tool fetches planner events over a date range, with a default week-long window. It distinguishes itself from other planner-related tools by specifying the range and the enrichment behavior.

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?

The description implicitly conveys when to use it (for date-range queries) and the default fallback, but doesn't explicitly contrast with list_planner_events or other siblings. Still, the purpose is evident enough for selection.

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