Skip to main content
Glama
Sign In
harristeeter-mcp

harristeeter-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ht_get_recipe

Read-only

Retrieve a Harris Teeter recipe's ingredients, steps, times, servings, and matched store-product UPCs, making it ready to add the required items to a cart.

Instructions

Read a Harris Teeter recipe: ingredients, steps, times, servings, and the store products (UPCs) matched to each ingredient — ready for ht_add_to_cart.

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": {
      "id": "<id>"
    },
    "name": "ht_get_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecipe id from ht_search_recipes.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/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 agent knows this is a safe open-world read. The description adds useful context about the returned payload and that products are UPC-matched for cart use, but says nothing about failure modes, missing recipes, or upstream variability for an open-world read.

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?

A single dense sentence, front-loaded with verb and resource, with the payload enumerated inline and the follow-on action stated last. No wasted wording.

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?

With no output schema, the description carries the burden of describing return values and does so: ingredients, steps, times, servings, UPC matches. Combined with safety annotations and a fully documented 2-parameter schema, an agent has what it needs; only error/empty-recipe behavior is unaddressed.

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% — both id (pattern, provenance) and view (enum semantics) are fully documented in the schema. The description adds no parameter-level detail beyond that, so the baseline 3 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 ('Read a Harris Teeter recipe') followed by an enumeration of exactly what comes back: ingredients, steps, times, servings, and UPC-matched products. It also implicitly separates this from the search tool by tying the id parameter to ht_search_recipes.

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?

'Ready for ht_add_to_cart' gives a clear downstream workflow cue: call this after finding a recipe and before adding to cart. It stops short of naming alternatives or stating when not to use it (e.g., to just browse recipes), so it falls short of full routing 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