Skip to main content
Glama
Sign In
harristeeter-mcp

harristeeter-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ht_get_weekly_ad

Read-only

Retrieve this week's Harris Teeter weekly ad by department, or omit it to review all specials; filter by item title to locate specific deals.

Instructions

Read this week's Harris Teeter weekly ad (Weekly Specials) at your store, by department: 1 Produce, 2 Breads & Bakery, 3 Deli, 4 Dairy & Chilled Foods, 5 Frozen Foods, 6 Meat - Packaged, 7 Meat - Fresh, 8 Seafood, 9 Breakfast Foods, 10 Meal Makers, 11 Baking Items, 12 Snacks & Sweets, 13 Beverages, 14 Beer & Wine, 15 Household Essentials, 16 Pet Essentials, 17 Health Care Essentials, 18 Beauty Care Essentials. Omit department for every department.

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

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.
searchNoOnly items whose title mentions this, e.g. "chicken".
departmentNoDepartment number (see description).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/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 "this week" and to "your store" (session store context), which is useful beyond the annotations, but says nothing about pagination, result size, or whether unlisted items appear.

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?

One front-loaded sentence with the resource first and the department table after; the long enumeration earns its place because the enum values are otherwise opaque. Minor waste in repeating "Essentials" across many entries, but nothing is misleading or padded.

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 3-optional-parameter read tool with no output schema, the description covers the only hard-to-infer part (department codes) and the default. The view and search parameters are handled by schema text, and return-value shape is left undescribed, which is acceptable given no output schema exists but leaves some uncertainty.

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?

Schema coverage is 100%, so the baseline would be 3, but the description does necessary work the schema cannot: the department enum's own description just says "see description," and the description supplies the full 1–18 code-to-department mapping, plus the omit-for-all behavior. Search and view semantics are left entirely to 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?

States a specific verb and resource ("Read this week's Harris Teeter weekly ad (Weekly Specials)") plus scope ("at your store", "this week's"). It does not name the close sibling ht_list_specials, so an agent gets no explicit rule for choosing between the weekly ad and the specials list, but the resource itself is unambiguous.

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?

Gives an explicit default rule for the one optional filter ("Omit department for every department"), which is real when-to-use guidance for the main parameter. It stops short of saying when to use this tool over ht_list_specials or ht_get_products, so it is clear context without exclusions/alternatives.

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