Skip to main content
Glama

Compare UK deals for a phone

find_phone_deals
Read-onlyIdempotent

Every deal UK retailers list for one phone on Vouchernaut's phone finder: monthly price with its upfront cost, contract length, total cost over the contract with announced price rises included (and each rise in pounds and month), data, network and seller, with a tracked link to the retailer. Filter by storage, colour, condition, budget, network, contract length and data.

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": {
      "phone": "<phone>"
    },
    "name": "find_phone_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoLowest total cost (default), lowest monthly, lowest upfront, or most datatotal
limitNoDeals to return
phoneYesThe phone, e.g. "iPhone 16", "Galaxy S25 Ultra"
colourNoColour as the retailers name it
monthsNoContract length in months (1 is monthly rolling)
networkNoOnly plans on this network (brands on it, like iD Mobile on Three, count)
storageNoStorage in GB
upgradeNoDeals for customers already on the network
min_dataNoAt least this many GB a month, or unlimited
conditionNo
max_monthlyNoMost a month, in whole pounds
max_upfrontNoMost upfront, in whole pounds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a safe, idempotent, non-destructive, closed-world read. The description goes beyond them by disclosing what the results contain, notably total cost with announced price rises itemised in pounds and month, plus tracked retailer links. It does not discuss pagination or result ordering, but that is minor given the annotation coverage.

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?

Two sentences, front-loaded with the returned payload before the filter list. Dense but every clause carries information; the parenthetical about price rises is long but is the tool's differentiating detail.

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 12 parameters and no output schema, the description carries the return-shape burden and does so with a concrete field inventory (monthly price, upfront, contract length, total cost, data, network, seller, tracked link). Only sorting/limit behaviour and result ordering are left unaddressed.

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 92%, so the schema already documents nearly every parameter. The description restates the filter dimensions (storage, colour, condition, budget, network, contract length, data) without adding format or value constraints beyond what the schema supplies, so baseline 3 applies.

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?

States a specific verb and resource ('every deal UK retailers list for one phone'), names the service (Vouchernaut's phone finder), and implicitly separates itself from the SIM-only sibling by scoping to deals 'for one phone'. It stops short of naming the alternative, so an agent must infer the SIM-only boundary.

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?

Usage is only implied: the filter list ('Filter by storage, colour, condition, budget, network, contract length and data') tells the agent what the tool can be narrowed to, but there is no when-to-use guidance and no mention of when to prefer sim_only_deals or price_drops instead.

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