Skip to main content
Glama
chrischall

myhotlunchbox-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mhlb_set_subscription_enabled

Destructive

Turn recurring lunch subscriptions on or off to control whether future lunches are automatically ordered and charged.

Instructions

Turn recurring lunch subscriptions on or off for the account. Turning it ON means future lunches are ordered and charged automatically. 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
enabledYestrue to enable recurring subscriptions, false to disable.
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.

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

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

The description discloses the confirmation behavior, including the two-step fallback with confirmToken, and warns that the write is UNVERIFIED with a request shape derived from compiled API client. This goes well beyond the annotations (readOnlyHint=false, destructiveHint=true) by explaining the exact behavior and risk. No contradictions with annotations.

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 dense but every sentence carries critical information: purpose, confirmation flow, fallback mechanism, and the unverified warning. It is front-loaded with the core action and the warning is placed last. No fluff or redundancy.

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 write tool with a confirmation flow and an unverified implementation, the description covers all necessary operational details: the two-step process, the meaning of confirmToken, and the caution to inspect the preview. It also references MCP_CONFIRM_MODE for further context. No output schema exists, so return values aren't required, and the description doesn't claim them.

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 description coverage is 100%, so the schema already documents both parameters. The description adds meaning by explaining that 'enabled=true' means future lunches are ordered and charged automatically, and it elaborates on confirmToken usage, including never inventing or reusing tokens. This provides context beyond the bare schema definitions.

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 tool's action: 'Turn recurring lunch subscriptions on or off for the account,' specifying both the verb and the resource. It distinguishes itself from sibling tools like mhlb_get_subscription_settings (read) and mhlb_list_subscriptions (list) by focusing on the write operation. The purpose is immediately clear and unambiguous.

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 provides explicit context on when to use the tool: to change subscription status, and it details the confirmation flow. However, it does not explicitly name alternatives or state when not to use this tool, though it's implied by the action. The note about inspecting the confirmation preview before approving is a useful safety guideline.

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