Skip to main content
Glama
Sign In
harristeeter-mcp

harristeeter-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ht_start_checkout

Reserves a Harris Teeter pickup window and creates a checkout draft for the current cart, returning real totals and a review link. The order is not placed or charged; the user confirms and completes it on harristeeter.com.

Instructions

Reserve a Harris Teeter pickup window and create the checkout for the current cart. Returns the real totals (coupons, fees, tax) and a link; the order is NOT placed and nothing is charged — the user reviews it and presses "Place Order" on harristeeter.com. 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).

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": {
      "window": "<window>"
    },
    "name": "ht_start_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowYesThe pickup window exactly as ht_list_timeslots returned it, e.g. "2026-11-12T22:00:00Z/2026-11-12T23:00:00Z".
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. First observedv0.3.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that real totals and a link are returned, that no charge occurs, and that the order is only placed later on harristeeter.com. It also documents the two-phase confirmation behavior and the confirmToken fallback, which 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-loads the action and the safety boundary, then the confirmation mechanics. Dense but nearly every clause carries information; the trailing MCP_CONFIRM_MODE reference is slightly compressed but still useful.

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 supplies the return shape (totals, fees, tax, link) and the full confirmation protocol, so an agent has everything needed to call it correctly and safely.

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; the description adds real value by explaining the confirmToken lifecycle (only after a preview, never on the first call, never invented or reused) and the MCP_CONFIRM_MODE context that governs when it 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?

States a specific verb and resource ('Reserve a Harris Teeter pickup window and create the checkout for the current cart') and immediately bounds the effect ('the order is NOT placed and nothing is charged'), which separates it from a true order-placement tool without needing to name a sibling.

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 clear preconditions: the window must come from ht_list_timeslots, and the user must confirm before proceeding. It does not explicitly route the agent to ht_get_checkout for reviewing an existing checkout, so it stops short of full when/when-not guidance.

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