Skip to main content
Glama
evcraddock

mealplan-mcp

by evcraddock

export_mealplans_to_pdf

Export meal plans for a specific date range into a PDF file. Provide a start and end date to generate a downloadable document of your scheduled meals.

Instructions

Export meal plans within a specified date range to a PDF file.

Args:
    date_range: Dictionary containing start and end dates in format YYYY-MM-DD
        - start: Start date (required)
        - end: End date (required)

Returns:
    JSON string containing either:
    - Success: {"ok": "path/to/generated.pdf"}
    - Error: {"error": "error_type", "message": "error_description"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_rangeYes
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It mentions the export action and returns a JSON string, but it does not disclose whether the tool has side effects (e.g., file creation location, overwrite behavior), authorization requirements, or whether it is read-only or destructive. The absence of these details leaves significant behavioral gaps.

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?

The description is concise, with the main action in the first sentence. The Args and Returns sections are clearly delineated and add necessary detail without unnecessary verbosity. It is well-structured and front-loaded, though the Returns section could be slightly more compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has one parameter with a nested object, no output schema, and no annotations, the description covers the parameter format and return structure adequately. However, it lacks details on behavior like file naming, location, error types, and potential side effects, making it minimally complete for an agent to use safely without further context.

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?

The input schema provides only a loose object type with no description of its keys. The description compensates fully by specifying the exact structure ('dictionary containing start and end dates'), the date format ('YYYY-MM-DD'), and which keys are required. This adds essential meaning beyond the schema.

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 action ('Export'), the resource ('meal plans'), the format ('to a PDF file'), and the scope ('within a specified date range'). This distinguishes it from sibling tools like 'list_mealplans_by_date_range' which lists but does not export.

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?

The description implies the tool is used when a PDF export of meal plans is needed, but it does not explicitly state when to use it versus alternatives (e.g., listing meal plans) or provide any explicit 'when not to use' or prerequisite conditions. The guidance is implicit rather than prescriptive.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/evcraddock/mealplan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server