Skip to main content
Glama

Search coupon codes and deals

search_coupons
Read-onlyIdempotent

Find current coupon codes and deals (offers without a code, e.g. free shipping) by keyword and/or store name, optionally for one country. A keyword also matches store names, so "vpn" finds NordVPN. Returns up to 10 active offers (at most 3 per store unless a store is given) with code (or none), end date, countries and links, and says when there are more. Covers coupon codes and deals, not individual products on sale.

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

Input Schema

NameRequiredDescriptionDefault
queryNoKeyword, e.g. "shoes" or "free shipping"
storeNoStore name or domain, e.g. "example.com"
countryNoISO country code, e.g. CH or US. Returns offers for that country plus worldwide ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, non-open-world, so the safety profile is covered. The description goes well beyond that with result-shape behavior an agent cannot get from structured fields: a 10-offer cap, a 3-per-store cap unless a store is specified, the returned fields (code or none, end date, countries, links), and an explicit signal when more results exist.

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 tightly packed sentences with no filler: purpose first, matching semantics second, return shape and scope boundary last. Dense, but each clause carries operational information an agent needs.

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-value burden and does so fully: result fields, count limits, per-store throttling, and truncation signaling. Combined with complete parameter documentation, nothing needed to call this correctly is missing.

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% and the country parameter's additive behavior (country offers plus worldwide) is already documented there. The description still adds real meaning beyond the schema by explaining that a keyword also matches store names, e.g. 'vpn' finds NordVPN, which changes how an agent should construct the query.

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 ('Find') and resource ('current coupon codes and deals'), and immediately disambiguates the resource by clarifying that deals can be codeless offers like free shipping. The closing sentence explicitly excludes individual products on sale, drawing the line against search_products.

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?

The final sentence ('Covers coupon codes and deals, not individual products on sale') gives an explicit when-not-to-use rule that routes the agent to search_products. No sibling is named directly and there is no positive 'use this when you need X' framing, so routing is clear but slightly inferential.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.