harristeeter-mcp

Overview Schema Source Related Servers Discussions Admin

ht_oa_list_menu

Read-only

List Order Ahead menu items for a single department, grouped by category, including name, price, unit, and serving size.

Instructions

List the Order Ahead menu for one department — items with name, price, unit and serving size, grouped by category.

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": {
      "departmentId": "<departmentId>"
    },
    "name": "ht_oa_list_menu"
  }
}

Input Schema

Name	Required	Description	Default
`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.
`departmentId`	Yes	From ht_oa_list_departments.

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 safety is covered. The description contributes useful behavioral detail about the response (field set and category grouping), but says nothing about the effect of the `view` modes, pagination, or size limits on a per-department menu.

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 sentence with the resource and scope front-loaded and the returned fields appended as a compact clause. No filler, no restatement of the tool name.

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's listing of returned fields and grouping does real work and is largely sufficient for a simple read-only list call. Minor residual gaps are the unexplored `view` behavior and result volume, which the schema partially covers.

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 both parameters are already documented, including the enum values for `view`. The description only implies the departmentId requirement through "for one department" and adds no format or example detail beyond the schema; baseline 3 applies.

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?

The description uses a specific verb ("List") and a specific resource ("the Order Ahead menu") scoped to "one department", then names the fields returned (name, price, unit, serving size) and the grouping (by category). That is enough for an agent to distinguish it from a single-item lookup like ht_oa_get_item, but it never explicitly contrasts itself with other catalog-style siblings.

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

Usage Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance and no named alternative. The only scoping cue is "for one department", which is a purpose constraint rather than guidance; nothing tells the agent when to prefer this over ht_get_products or ht_oa_get_item for a specific item.

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