Skip to main content
Glama

ShopAt UK Deals

List Digidip vouchers (worldwide)

list_vouchers
Read-only

Paginate GLOBAL voucher codes (Digidip + open-source feeds). Optional countries (ISO-3166 Alpha-2); omit for all. Each row ALWAYS includes voucher_code and url/go_url — always send both (required for ChatGPT/LLMs). url = ShopAt → Digidip wrap.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
countryNo
countriesNoOptional ISO-3166 Alpha-2 country codes. Empty/omit = all countries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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, and the description adds genuinely new behavior: results are limited to global feeds and every row is guaranteed to carry both voucher_code and url/go_url, with url described as the ShopAt→Digidip wrapper. With no output schema, these return-shape guarantees are the main behavioral value. It still omits ordering, truncation risk, and how pagination exhaustion manifests.

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 short sentences, front-loaded with the verb, scope, and filter behavior; nothing is buried. The parenthetical '(required for ChatGPT/LLMs)' is redundant noise that adds no semantic content for an agent.

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

Completeness3/5

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

For a four-parameter, no-output-schema read tool, the definition covers the essentials of what comes back and how to filter. It is incomplete on pagination semantics and result ordering, which matter for a 'paginate' tool where page/limit are the primary controls.

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 only 25%, and the description clarifies the country/countries semantics ('omit for all'), which compensates for half of the documentation gap. It says nothing about page or limit, whose behavior (defaults 1 and 50, max 100) is only visible in the schema types without explanation of ordering or total counts.

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 ('Paginate GLOBAL voucher codes') plus the data provenance ('Digidip + open-source feeds'), which lets an agent distinguish this bulk listing from a filtered search. It stops short of naming a sibling as the alternative, so differentiation is implicit rather than explicit.

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

Usage Guidelines2/5

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

'Optional countries... omit for all' tells the agent how to filter, but never when this tool should be chosen over search_vouchers or get_voucher. There is no statement of when-not-to-use, cost, or expected result ordering, so selection between siblings 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources