CouponLlama: Shopper-Rated Promo Codes

Find promo codes for a store

find_promo_codes

Read-only

Live promo codes for one online store, best offer first. Accepts the store's name, its website (“store.com”) or any URL on it. Each code comes with what it gives, its conditions, how many shoppers said it worked and when it last worked. When no store matches, it says so and suggests close matches instead of guessing.

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": {
      "store": "<store>"
    },
    "name": "find_promo_codes"
  }
}

Input Schema

Name	Required	Description	Default
`store`	Yes	Store name, domain or any URL on the store's site, for example “Huega House”, “huegahouse.com” or a link to a product page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description goes further by disclosing result ordering, the fields returned per code (value, conditions, success count, last-worked date), and the no-match fallback that returns close matches rather than guessing. It stops short of covering pagination, result limits, or code freshness beyond the word 'live'.

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?

Three tight sentences with no filler, opening with the core purpose and ordering, then input forms, then return content and the failure case. Every sentence carries information an agent would act on.

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?

With a single required parameter, no output schema, and a lightweight annotation set, the description supplies everything needed: what it returns, how results are ordered, and what happens on a miss. No material gap remains for correct invocation.

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 coverage is 100% and the parameter description already gives the same three accepted forms with examples. The description restates the name/domain/URL flexibility without adding constraints or edge-case handling, so it is baseline rather than additive.

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 concrete verb and resource ('Live promo codes for one online store') plus an ordering rule ('best offer first'), so an agent knows exactly what it returns. It does not name or contrast with the sibling 'latest_promo_codes', so the distinction from that tool must be inferred.

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 only implied: the tool is for looking up codes for a single store, and the accepted input forms are listed. There is no explicit when-to-use/when-not guidance and no mention of alternatives such as latest_promo_codes or search_stores when the store is unknown.

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?