Skip to main content
Glama
mgwalkerjr95

Texas Grocery MCP

by mgwalkerjr95

coupon_list

Read-only

List available HEB digital coupons with discount details, descriptions, and expiration dates. Filter by category to find coupons in specific departments.

Instructions

List available HEB digital coupons.

Returns coupons with discount details, descriptions, and expiration dates. Filter by category to find coupons in specific departments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum coupons to return
categoryNoFilter by category name (e.g., 'pantry', 'health & beauty') or ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint=true, so description adds value by specifying return fields (discount details, descriptions, expiration dates). No contradiction with annotations.

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?

Two concise sentences, front-loaded with purpose, followed by return content and filtering capability. No unnecessary words.

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 output schema present, description adequately covers purpose, return content, and filtering. Could mention pagination implications of limit parameter, but not essential.

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 parameters are already documented. Description reinforces category filtering but adds no new semantic information beyond the schema.

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?

Description clearly states 'List available HEB digital coupons' with specific verb and resource. It distinguishes from siblings like coupon_search or coupon_clip by focusing on listing all coupons with details.

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?

Implies use for browsing or filtering coupons by category, but does not explicitly state when not to use or mention alternatives. No comparison to sibling tools like coupon_search for targeted searches.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mgwalkerjr95/texas-grocery-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server