List planned meals with their date, meal slot, linked recipe or custom name, servings and notes. Narrow with from and to.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | Inclusive date range end (format: YYYY-MM-DD). Omit for an open-ended end. | |
| from | No | Inclusive date range start (format: YYYY-MM-DD). Omit for an open-ended start. |
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | ||
| title | No | ||
| message | No | ||
| variant | No |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "from": "2026-07-14",
+ "to": "2026-07-21"
+ }
+]Input schema / properties / from / descriptionPrevious value: -"Inclusive date range start (format: YYYY-MM-DD)"New value: +"Inclusive date range start (format: YYYY-MM-DD). Omit for an open-ended start."Input schema / properties / from / examplesAdded value: +[
+ "2026-07-14"
+]Input schema / properties / to / descriptionPrevious value: -"Inclusive date range end (format: YYYY-MM-DD)"New value: +"Inclusive date range end (format: YYYY-MM-DD). Omit for an open-ended end."Input schema / properties / to / examplesAdded value: +[
+ "2026-07-21"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context about the data returned and optional date filtering, but it does not disclose potential behaviors like ordering, pagination, or how omissions of from/to are handled beyond what the schema states.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences with no filler. It front-loads the primary purpose and follows with the optional narrowing capability, making it easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only list tool with an output schema, complete parameter documentation, and safety annotations, the description is fully adequate. It covers what is listed, the key filter options, and leaves nothing essential missing for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and both parameters are fully documented with format, inclusivity, and omission behavior. The description's 'Narrow with from and to' adds little beyond the schema, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action ('List planned meals') and identifies the resource and returned fields (date, meal slot, linked recipe or custom name, servings, notes). It is unambiguous even though it does not explicitly differentiate from sibling list tools by name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool's use case by explaining what it lists and how to narrow results with from and to. It does not explicitly mention alternatives or when not to use this tool, but the purpose is clear enough for an agent to select it appropriately among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.