CouponLlama: Shopper-Rated Promo Codes

Search stores

search_stores

Read-only

Stores CouponLlama covers that match a name or a category, with how many live codes each has and its best offer. Use it to browse (“which pet stores have codes?”) or when the user isn't sure of a store's exact name.

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": "search_stores"
  }
}

Input Schema

Name	Required	Description
`limit`	No	How many stores to return, 1 to 50. Defaults to 20.
`query`	No	Part of a store's name, or words about what it sells.
`category`	No	A category slug from list_categories, such as “pets” or “home-garden”.
`with_codes_only`	No	Leave out stores with no live code. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description is consistent with that by describing a closed catalog of stores CouponLlama 'covers'. It goes beyond the annotations by disclosing the shape of each returned record (live code count plus best offer). It says nothing about result ordering, pagination, or what happens when a query matches nothing.

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 sentences, zero filler, and the capability statement comes before the usage cue. The parenthetical example question is doing real work rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the return-shape burden itself and does so by naming live code counts and the best offer. With four optional parameters fully documented in the schema and the safety profile covered by annotations, an agent has everything needed to select and call this tool.

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 the baseline is 3 regardless. The description adds marginal meaning by framing the match as a name-or-category lookup and by motivating the fuzzy query ('when the user isn't sure of a store's exact name'), but it adds no detail on limit, category slugs, or the with_codes_only default beyond what the schema states.

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 names a specific verb and resource ('Stores CouponLlama covers that match a name or a category') and adds what each result carries ('how many live codes each has and its best offer'). It is clear enough to separate from a code-lookup tool, but it never names a sibling, so the differentiation is inferred rather than stated.

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?

It gives two concrete usage cues: browsing ('which pet stores have codes?') and name uncertainty. That is a real when-to-use signal with examples rather than vague description. It stops short of naming an alternative tool for exact-name or exact-code lookups, so there are no explicit exclusions.

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

All CouponLlama: Shopper-Rated Promo Codes tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?