Skip to main content
Glama
Sign In
harristeeter-mcp

harristeeter-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ht_rx_request_refill

Destructive

Request a prescription refill for pickup at a Harris Teeter pharmacy, paid at the counter. Requires an active pharmacy session and user confirmation before the refill is submitted.

Instructions

Request a refill of a prescription for pickup at its Harris Teeter pharmacy, paid at the pharmacy. The pharmacy starts work on it and there is no cancel from here. Needs an active pharmacy session. NOT yet verified against a live refill: the first real request is the test. 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": {
      "rxNumber": "<rxNumber>",
      "pickupDate": "<pickupDate>",
      "pickupTime": "<pickupTime>"
    },
    "name": "ht_rx_request_refill"
  }
}

Input Schema

NameRequiredDescriptionDefault
rxNumberYesRx number from ht_rx_list_prescriptions.
pickupDateYesYYYY-MM-DD, today or later, during pharmacy hours.
pickupTimeYese.g. "3:30 PM".
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.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds substantial context beyond them: the pharmacy begins processing immediately, the action is irreversible from this tool, the endpoint is unverified against a live refill, and the confirmation handshake (elicitation prompt or preview + confirmToken) is spelled out. Missing only what a successful submission returns.

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?

Purpose and irreversibility are front-loaded, and every sentence carries operational weight. The final sentence about confirmation modes is dense and parenthetical, which costs a little readability but not correctness.

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?

For a destructive, unverified mutation with no output schema, the description covers prerequisites, irreversibility, confirmation flow, and test status. The one gap is that it does not say what a completed refill call returns (e.g., a request/confirmation identifier or pickup instructions).

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% and all four parameters are documented in the schema, including confirmToken's provenance rules. The description restates the two-step confirmation semantics but adds no new format or value guidance beyond what the schema already carries, so the baseline 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?

Specific verb plus resource plus payment/pickup scope; an agent can select it without opening the schema.

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 real preconditions and exclusions: an active pharmacy session is required, and there is no cancel path from here once submitted. It stops short of naming an alternative tool for viewing or cancelling refills, so it is clear but not fully routing.

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