Skip to main content
Glama
myhotlunchbox-mcp

myhotlunchbox-mcp

by chrischall

mhlb_print_orders

Generate a printable PDF of lunch order details for one date and selected students, returning a file path, base64, or expiring download link.

Instructions

Generate the printable order-details PDF for a single lunch date. Note this is one date, not a range, and studentIds is required — the endpoint fails if it is empty, or if no order matches the date and status you ask for. Get both from mhlb_get_calendar. Locally the PDF is written to disk and its path returned (or the bytes inline as base64 with inline: true); on a hosted server it comes back as a signed, expiring download link (url, expiresAt).

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": {
      "date": "<date>",
      "studentIds": "<studentIds>"
    },
    "name": "mhlb_print_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesThe lunch date to report on (YYYY-MM-DD).
inlineNoReturn the PDF as base64 in the result instead of writing it to a file. Default false. On a hosted server a report over the inline limit comes back as a download link instead.
filenameNoOutput filename. Defaults to "Orders Details <date>.pdf".
studentIdsYesStudents to include — at least one. An empty list makes the endpoint fail.
orderStatusNoOrder status to report: 0 = Pending, 1 = Paid (default), 2 = Credited.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.1
    • changedInput schema / properties / inline / description
      Previous value: -"Return the PDF as base64 in the result instead of writing it to a file. Default false."New value: +"Return the PDF as base64 in the result instead of writing it to a file. Default false. On a hosted server a report over the inline limit comes back as a download link instead."
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.2.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description goes well beyond them: locally it writes a PDF to disk and returns the path, inline:true returns base64, and a hosted server returns a signed expiring link (url, expiresAt) — plus the failure conditions on empty studentIds and no matches. That is exactly the kind of side-effect and deployment-dependent behavior the annotations cannot express.

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 purpose, then constraints, then return shapes — no filler. The final sentence is dense with three return modes but every clause carries information an agent needs given there is no output schema. Slightly heavy but not wasteful.

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

Completeness5/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 correctly spends its budget explaining the three possible return shapes and the disk-write side effect, plus the failure modes. Nothing an agent needs to invoke this correctly or interpret the result is missing.

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 is 3, but the description adds real meaning: it flags studentIds as required and hard-failing when empty, and states that date must be a single date rather than a range. It also tells the agent where to source both values (mhlb_get_calendar), which the schema does not.

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 verb and resource with scope: "Generate the printable order-details PDF for a single lunch date." The 'order-details' qualifier distinguishes it from the sibling print tools (print_calendar, print_transaction), and "one date, not a range" pins the scope further.

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?

Gives concrete preconditions and provenance: get date and studentIds from mhlb_get_calendar, and the endpoint fails if studentIds is empty or nothing matches the date/status. It stops short of naming an explicit alternative report tool with a when-to-use contrast, but the guidance an agent needs to actually call it is present.

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