Skip to main content
Glama

ShopAt UK Deals

Get one deal

get_deal
Read-only

Get full details for one published ShopAt deal by numeric id or slug: price, was-price, discount, voucher code, store, keywords, expiry, ShopAt page and tracked outbound link.

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

Input Schema

NameRequiredDescriptionDefault
idYesDeal id (e.g. "3562") or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/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 by structured data. The description contributes the scoping adjective 'published', which tells the agent draft/unpublished deals will not be returned, but it says nothing about error behavior for missing ids or about the outbound link being tracked in a way that affects the caller.

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?

A single front-loaded sentence with the verb, resource, lookup key, and returned fields in that order, and no filler. Every clause carries information the agent can use.

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 one parameter, full schema coverage, and no output schema, the enumerated field list effectively documents the return payload, which is the main gap a description must fill here. The remaining omission, behavior on unknown or unpublished ids, is minor for a read-only lookup.

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 schema already documents the single 'id' parameter with an example and slug support. The description's 'by numeric id or slug' restates that rather than adding format, normalization, or fallback rules, so the baseline 3 applies.

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 ('Get') and resource ('one published ShopAt deal') plus the lookup key, then enumerates the payload. The word 'one' scopes it against the list-style siblings (search_deals, hot_deals, my_submissions), so an agent can tell a single-record fetch from a listing without opening a schema.

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: 'one published ... deal' signals a single-record lookup, and the required id makes the fetch pattern obvious. There is no explicit when-to-use or when-not guidance, no pointer to search_deals for discovery, and no note on what happens for unpublished or unknown ids.

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