harristeeter-mcp

Overview Schema Source Related Servers Discussions Admin

ht_get_products

Read-only

Look up Harris Teeter products by UPC to retrieve current price, sale price, size, unit price, and pickup-store stock for one or more items.

Instructions

Look up Harris Teeter products by UPC — price, sale price, size, unit price and stock at your pickup store.

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": {
      "upcs": "<upcs>"
    },
    "name": "ht_get_products"
  }
}

Input Schema

Name	Required	Description
`zip`	No	Price at the Harris Teeter nearest this ZIP, for this call only (needs Kroger API credentials).
`upcs`	Yes	UPCs to look up.
`view`	No	Response 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.
`locationId`	No	Price at this 8-digit store location id, for this call only (needs Kroger API credentials).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 13, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results are scoped to "your pickup store," which is genuinely useful context about pricing/stock variability, but it omits the 50-UPC batch cap and that zip/locationId overrides need Kroger API credentials.

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?

A single front-loaded sentence with the lookup key first and the returned fields after, with no wasted words. Its only cost is omission rather than verbosity, so conciseness itself is fine.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four fully documented parameters, read-only annotations, and no output schema, the description's field list is a helpful complement. However, for a batch lookup tool it should mention the 50-item limit and the store/credential dependency for zip and locationId overrides, both of which affect how an agent calls it.

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 100%, so every parameter including the view enum and the zip/locationId override semantics is already documented, making 3 the baseline. The description's "at your pickup store" phrase corroborates the default store scoping but adds no syntax or format detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Look up Harris Teeter products by UPC" states a specific verb, resource, and lookup key, and enumerates returned fields (price, sale price, size, unit price, stock). It implicitly distinguishes itself from ht_search_products by requiring UPCs rather than a query, but never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the schema notes UPCs come "as returned by ht_search_products," suggesting this is a follow-up detail call, but the description itself gives no when-to-use or when-not-to-use guidance. An agent must infer that searching comes first and looking up comes second.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.