Whale Coupons

Find coupon codes for a store

find_coupons

Read-onlyIdempotent

Use this when the user wants a coupon, promo, discount or voucher code for a specific online store or brand, or shares a store's website or product page URL and asks about saving on it. Accepts a store name ("Airwheel Luggage"), a domain ("airwheel-luggage.com") or a full product URL. Returns up to 3 matching stores, each with the code, the discount, how to apply it, minimum order if any, an affiliate shop link and the Whale Coupons store page. If no store has that name the result says so (found=false); when the words describe a product, stores that sell it may be returned instead (match="product"). Never invent or guess a code. Covers thousands of independent online stores, updated daily; large general marketplaces are not covered. For a product type rather than a store (e.g. "headphones") use search_stores. Do not use for price comparison, product reviews, order tracking or buying on the user's behalf.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`store`	Yes	Store or brand name, website domain, or a product/store page URL, exactly as the user gave it. Examples: "Saguaro Barefoot Shoes", "saguaro.com", "https://www.saguaro.com/products/...". Do not add words like 'coupon' or 'code'.

Output Schema

TableJSON Schema

Name	Required	Description
`found`	Yes
`match`	No	exact/partial: store name or website matched; product: no store with that name, results are stores whose own catalog lists that product.
`query`	No
`results`	Yes
`disclosure`	Yes
`suggested_category`	No	When no store matched but the query looks like a product type: the closest category to use with search_stores.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 18, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial context beyond that: result cap of 3 stores, the found=false and match="product" edge cases, a 'never invent a code' guarantee, daily update cadence, and the coverage gap for large general marketplaces.

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?

Front-loaded with the triggering condition, then inputs, returns, edge cases, coverage and exclusions. Despite its length, each sentence carries distinct information an agent needs to select and call the tool correctly.

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?

Output schema exists, yet the description still summarizes return contents and failure modes. Combined with full parameter and annotation coverage, an agent has everything needed to call it and interpret results.

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?

With one parameter at 100% schema description coverage, the schema already documents accepted formats and examples. The description restates the same accepted inputs (store name, domain, URL) without adding syntax or validation detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('find coupon codes') plus the accepted inputs (store name, domain, product URL). It distinguishes itself from sibling search_stores by scoping to coupons for a specific store rather than a product type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gives when-to-use (user wants a coupon/promo/discount code or shares a store URL), names the alternative (search_stores for a product type), and lists exclusions (price comparison, reviews, order tracking, buying on the user's behalf). Nothing is left to inference.

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

All Whale Coupons 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.