Skip to main content
Glama
Sign In
harristeeter-mcp

harristeeter-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ht_list_coupons

Read-only

Lists Harris Teeter e-VIC digital coupons by status—unclipped, clipped, or all—with brand, value, and expiry. Filter by search text to find coupons, then clip them to your card.

Instructions

List Harris Teeter e-VIC digital coupons — available (unclipped), clipped to your card, or all — with brand, value and expiry. Use ht_clip_coupon to load one to your card.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ht_list_coupons"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands; "raw" returns the upstream payload unprojected. compact returns a projection of the documented fields; "full" returns the API payload minified; "raw" pretty-prints it.
limitNo
offsetNo
searchNoFilter by text, e.g. "coffee".
statusNounclipped

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only and open-world safety, and the description adds useful context beyond them: it discloses the three coupon states and which attributes (brand, value, expiry) are surfaced. It does not mention pagination defaults or result caps, which the limit/offset parameters imply.

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 short sentences with zero filler: the scope and returned fields come first, and the sibling routing comes last. Every clause earns its place.

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 read-only list tool with no output schema, the description covers purpose, the meaningful status dimension, and the mutation counterpart, which is sufficient to call it correctly. Minor gaps remain around pagination and the 'view' projection modes, but the schema does define these.

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 description coverage is only 40%, and the description clarifies the semantics of 'status' (mapping unclipped to available and clipped to card-linked). It says nothing about 'view', 'search', 'limit' or 'offset', leaving most of the low-coverage surface undocumented in prose.

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 states a specific verb and resource ('List Harris Teeter e-VIC digital coupons') plus the three scoping modes (unclipped, clipped, all) and the fields returned (brand, value, expiry). An agent can distinguish it from ht_clip_coupon, the mutation sibling, without opening either 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?

It explicitly redirects to ht_clip_coupon for loading a coupon onto the card, which is a named alternative with its own condition. It does not, however, say when to prefer 'status' filtering versus the 'search' text filter, so some selection guidance is left implicit.

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