Skip to main content
Glama
chrischall

myhotlunchbox-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mhlb_init_checkout

Initiate checkout to preview order summary, totals, taxes, applied credits, and payment methods without charging. Confirm to proceed.

Instructions

Start checkout for the cart: returns the order summary, totals, taxes, applied credits and the available payment methods. This does NOT charge anything — it is the read step before mhlb_checkout. 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
orderIdsYesIds of the orders to pay for, from mhlb_get_cart.
couponCodeNoCoupon code to apply to this checkout.
checkoutTypeNoPayment method type, as mhlb_init_checkout reports it. Omit to let the server default.
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.
giftCardCodeNoGift card code to apply to this checkout.
schoolDonationsNoSchool donation selections, as returned by mhlb_init_checkout.

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.3/5.0
Behavior5/5

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

Annotations mark readOnlyHint=false, so it's a write; the description clarifies it does not charge but is still a write step. It discloses the confirmation prompt behavior and the two-step fallback with confirmToken, and adds a critical UNVERIFIED warning about the request shape. This goes well beyond the annotations and gives the agent actionable risk awareness.

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 dense but well-organized: purpose first, then confirmation flow, then a safety warning. Every sentence carries information; no filler, though it is slightly longer than minimal due to the necessary confirmation and unverified warnings.

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?

Given the confirmation complexity and the UNVERIFIED warning, the description covers the behavior an agent needs: what it returns, that it's a pre-checkout step, how confirmation works, and the risk. No output schema, but return values are listed. It's complete for this tool, though it could mention what happens if the cart is empty or invalid.

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 coverage is 100% with detailed descriptions for each parameter, including confirmToken's special semantics. The description itself doesn't add parameter-specific meaning beyond what the schema provides, so it stays at the baseline for high schema coverage.

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: 'Start checkout for the cart' and lists the returned data (order summary, totals, taxes, credits, payment methods). Explicitly distinguishes from sibling mhlb_checkout by calling itself 'the read step before mhlb_checkout', so an agent can tell them apart without inspecting schemas.

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?

Clearly indicates it is the first step before mhlb_checkout and does not charge. Describes the confirmation flow and references MCP_CONFIRM_MODE, giving explicit sequencing guidance. It doesn't mention when to use a non-checkout alternative like mhlb_get_cart, but the purpose is distinct enough that the agent can infer the right context.

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