Skip to main content
Glama

ShopAt UK Deals

Get one Digidip voucher

get_voucher
Read-only

Fetch one Digidip voucher by document id (any country). Always returns voucher_code and url/go_url together — LLMs must share both with the user.

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": {
      "id": "<id>"
    },
    "name": "get_voucher"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDigidip voucher document id (hex).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations only declare readOnlyHint=true and openWorldHint=false; the description adds a genuine behavioral contract beyond that: voucher_code and url/go_url always come back together and must both be relayed to the user. That is a real output/usage constraint not encoded in the schema or annotations. It stops short of covering not-found or error behavior, so it is not a 5.

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?

Two short sentences with no filler: the lookup key and scope come first, then the output-sharing requirement. Every clause carries actionable information and nothing is redundant.

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?

For a single-parameter read tool with no output schema, the description supplies the essential return-value contract that structured fields do not. Minor gaps remain around missing-id/miss behavior and whether the id is case-sensitive, but the core call path is fully covered.

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 100%, and the single id property is already documented as a hex Digidip voucher document id with maxLength 128, so the schema does the heavy lifting. The description adds only the scope nuance that the id is valid cross-country ("any country"), which is marginal added meaning.

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 states a specific verb and resource ("Fetch one Digidip voucher") and scopes it with the lookup key ("by document id"), which makes it distinguishable from list_vouchers and search_vouchers by implication. It does not explicitly name the sibling alternatives, which keeps it from a 5.

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?

The phrase "by document id (any country)" implies the precondition that the caller already holds a voucher document id rather than search criteria. However, there is no explicit statement of when to prefer this over search_vouchers/list_vouchers, nor any exclusion or fallback guidance.

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