Skip to main content
Glama

ShopAt UK Deals

Search Digidip vouchers (worldwide)

search_vouchers
Read-only

Search GLOBAL voucher codes (Digidip + open-source Caramel/YaPromo/c0upons/coupon-swarm, including USA Caramel feeds). Optional countries filter uses ISO-3166 Alpha-2 (GB, DE, US, …); omit for all. Each result ALWAYS includes voucher_code plus url/go_url — ChatGPT/LLMs must give users both. url is ShopAt-tracked and Digidip-wrapped.

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

Input Schema

NameRequiredDescriptionDefault
qNoKeywords: retailer, domain, code or offer text (min 3 chars for live Digidip search).
pageNo
limitNo
countryNoSingle country code alias for countries=[code].
countriesNoOptional ISO-3166 Alpha-2 country codes. Empty/omit = all countries.
advertiserNoFilter by advertiser name or domain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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, so safety is covered; the description adds genuinely non-redundant behavior: every result carries voucher_code plus url/go_url and callers must surface both, and url is ShopAt-tracked and Digidip-wrapped. That is meaningful disclosure about return shape and link semantics that the annotations cannot convey. It stops short of describing pagination, totals, or de-duplication across the multiple feeds. Note the mild tension between 'GLOBAL/worldwide' framing and openWorldHint=false, though the named fixed feed set plausibly justifies a closed-world reading rather than a contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with scope and sources, then filtering, then mandatory output handling. No filler sentences. The parenthetical source list is heavy but earns its place by telling the agent where results come from.

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 no output schema, the description correctly spends its budget describing the return contract (voucher_code plus url/go_url, both mandatory) and the tracking nature of the links. For a six-parameter, all-optional search tool this is close to complete; what remains missing is pagination/result-volume behavior and whether results are merged or ranked across the distinct feeds.

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 67% and the schema already documents q's 3-char minimum, the country alias, and the ISO-3166 Alpha-2 semantics of countries, so the description mostly restates structured data. It adds no detail on pagination interaction between page/limit, on how advertiser matching works, or on how country and countries combine. Baseline 3 is appropriate.

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 gives a specific verb and resource ('Search GLOBAL voucher codes') and identifies the underlying sources (Digidip plus open-source Caramel/YaPromo/c0upons/coupon-swarm feeds), which is far more informative than the title alone. It does not explicitly contrast itself with siblings such as list_vouchers or search_deals, so an agent must infer the search-vs-list boundary rather than read it.

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?

It gives one concrete usage rule — 'omit for all' on the countries filter — and a minimum query length for live Digidip search. Beyond that, there is no guidance on when to prefer this over list_vouchers, search_deals, or get_voucher, and no stated exclusions or prerequisites. Usage is implied by the word 'Search' rather than spelled out.

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.

Resources