Skip to main content
Glama
harristeeter-mcp
by chrischall

ht_oa_list_departments

Read-only

List available Harris Teeter Order Ahead departments at your store, including deli, bakery, platters, and holiday meals, with lead times and order cutoff times.

Instructions

List Harris Teeter Order Ahead departments at your store — deli counter, sandwich shop, pizzas, party and seafood platters, fruit baskets, bakery, holiday meals — with lead time and order cutoff. Order Ahead is paid at pickup.

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_oa_list_departments"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds value beyond them by disclosing what the response contains (lead time and order cutoff) and the payment model ("paid at pickup"), which shapes how an agent should relay results to a user.

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?

Two sentences, front-loaded with the verb and resource, with no filler. The em-dash enumeration of departments is long but earns its place by enabling keyword matching against user requests.

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 zero-parameter read tool with no output schema, the description covers purpose, returned fields (lead time, cutoff), and the payment context. It stops short of explaining ordering sequencing or how the returned departments feed into sibling tools, but nothing essential for invoking it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate beyond the implicit store context. Baseline for zero parameters applies, and "at your store" usefully clarifies that the store is derived from session rather than supplied.

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?

States a specific verb and resource ("List ... Order Ahead departments") and enumerates the department types so an agent can match user intent like "deli" or "fruit basket" directly. It implicitly separates itself from ht_oa_list_menu by scoping to departments rather than items, 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 implied: the phrase "at your store" signals this is the entry point before browsing a menu, and the department list suggests a discovery step. There is no explicit when-to-use/when-not guidance and no named alternative such as ht_oa_list_menu or ht_oa_list_pickup_times, so the agent must infer the ordering flow.

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