Skip to main content
Glama
chrischall

myhotlunchbox-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mhlb_list_gift_cards

Read-only

List gift card balances and statuses on your account. Codes are masked to the last 4 characters by default, with an option to reveal full codes when needed.

Instructions

List gift cards on the account — balances and status, with each code masked to its last 4 characters. Pass revealCodes: true only when the user needs a full code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
revealCodesNoReturn full gift-card codes instead of masked ones. A code is redeemable money; default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.1
    • addedInput schema / properties / revealCodes
      Added value: +{
+  "description": "Return full gift-card codes instead of masked ones. A code is redeemable money; default false.",
+  "type": "boolean"
+}
  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
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds valuable behavioral context: codes are masked by default and revealCodes exposes redeemable money, signaling a security-sensitive operation. No contradiction.

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?

Two sentences with no filler. The main action and output are front-loaded, followed by the precise conditional for the optional parameter.

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 read-only list tool with one optional boolean parameter and no output schema, the description covers the action, the masking behavior, and the reveal condition. Nothing an agent needs to call it correctly 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 covers revealCodes with 100% description coverage, explaining the default and security note. The description adds the conditional usage context ('only when the user needs a full code'), going slightly 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?

States a specific action (List), resource (gift cards), scope (on the account), and key output details (balances, status, masked codes). Clearly distinct from siblings like mhlb_apply_gift_card which operates on gift cards differently.

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?

Provides explicit conditional usage for revealCodes ('only when the user needs a full code'), which is direct guidance. Does not name alternatives, but no sibling list-gift-cards tool exists, so the context is sufficient.

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