Skip to main content
Glama
chrischall

myhotlunchbox-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mhlb_delete_order

Destructive

Cancel a school lunch order for a specific date or the entire recurring series. Requires confirmation before the cancellation is applied.

Instructions

Cancel a lunch order. If it was already paid for, the refund behaviour is whatever My Hot Lunchbox applies — this tool does not control it. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). NOTE: this write is UNVERIFIED — its request shape was derived from the web app’s compiled API client but has not been exercised against a live account. Inspect the confirmation preview before approving it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesOrder id, from mhlb_get_calendar or mhlb_get_cart.
eventDateYesThe lunch date of that order (YYYY-MM-DD).
studentIdYesStudent the order belongs to.
isRepeatedNotrue acts on the whole recurring series, not just this date. Defaults to false.
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.
isSubscribedNoWhether the order is a subscription. Defaults to false for mhlb_delete_order and true for mhlb_unsubscribe_order, matching what each is for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.1
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  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.5/5.0
Behavior5/5

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

The description discloses that refund behavior is outside the tool's control, that confirmation is required, and that the request shape is UNVERIFIED against a live account and was derived from the web app's compiled API client. This meaningfully supplements the annotations' destructiveHint and should change how an agent executes and approves the call.

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?

The description is longer than average, but every sentence earns its place: purpose, refund caveat, confirmation mechanics, fallback behavior, and the unverified-write warning. The core action is front-loaded, and the safety warnings appear before an agent would act.

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?

For a destructive write with no output schema, the description explains the full confirmation flow, what a fallback first call returns (preview plus confirmToken), and what to inspect before proceeding. Parameter details are fully covered by the schema, and the annotations cover destructive intent, so no critical operational information is missing.

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

Parameters3/5

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

Schema description coverage is 100%, and the parameter-level descriptions are already rich: confirmToken explains the exact two-step protocol, eventDate specifies the format, and isSubscribed gives per-tool defaults. The tool description adds no parameter-specific meaning beyond that, so the baseline 3 for high schema coverage applies.

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 opens with 'Cancel a lunch order', a specific verb and resource that unambiguously defines the operation. It also clarifies scope by noting that refund behavior is external and by distinguishing this cancellation tool from the subscription-focused sibling mhlb_unsubscribe_order.

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 gives clear process guidance for confirmation: use the client-supported prompt when available, or the two-step preview/confirmToken fallback otherwise, with explicit rules about never inventing or reusing the token. It does not explicitly enumerate when to prefer this over mhlb_unsubscribe_order, but the schema's isSubscribed description hints at that split, so the usage context is clear if not exhaustive.

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

Deploy Server

Other Tools