Skip to main content
Glama

ShopAt UK Deals

Submit a UK deal for moderation

submit_deal

Submit a UK deal to ShopAt. Requires an approved agent: send "Authorization: Bearer " (or a linked BoundProof credential) as an HTTP header on the MCP connection, never as a tool argument. UK only: GBP prices, direct https product URL on a UK retailer (.uk or a known UK-serving store), honest current and was prices, no spam. Submissions go to a moderation queue and are not public until approved. Duplicates from the last 14 days are refused. Returns the submission id and status.

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": {
      "title": "<title>",
      "url": "<url>",
      "price": "<price>",
      "merchant": "<merchant>",
      "description": "<description>"
    },
    "name": "submit_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDirect https:// product page on the UK retailer's site (no affiliate or short links).
priceYesCurrent price in GBP (0 for freebies).
titleYese.g. "Ninja AF100UK Air Fryer £69.99 at Argos".
categoryNo
currencyNoGBP
merchantYesRetailer name, e.g. "Argos".
image_urlNoOptional https product image.
was_priceNoGenuine previous price in GBP, if any.
expires_atNoOptional end date (ISO 8601).
descriptionYesPlain text: what it is, why it is a good price, any conditions.
voucher_codeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the auth mechanism (Bearer agent key or linked BoundProof credential, passed as an HTTP header and never as a tool argument), the moderation queue with the consequence that submissions are not public until approved, and the 14-day duplicate refusal. It also states the return value (submission id and status), which the annotations alone could not convey; nothing here conflicts with readOnlyHint=false, idempotentHint=false, or destructiveHint=false.

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?

Five tight sentences, front-loaded with purpose, then auth, then submission constraints, then moderation/duplicate outcomes, then the return value. No filler and no repetition of the title.

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 an 11-parameter, non-idempotent write with no output schema, the definition covers the high-risk items: authentication, moderation delay, duplicate rejection, and the shape of the response. Minor gaps remain around optional fields (category, expires_at, voucher_code, image_url), but nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 73%, so the baseline is 3, but the description adds real constraint meaning: prices must be GBP, the URL must be a direct https product page on a UK retailer (.uk or a known UK-serving store), and current/was prices must be honest. That sharpens the semantics of url, price, was_price and merchant beyond their schema text; category, expires_at and voucher_code remain unexplained.

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?

Opens with a specific verb and resource plus scope: 'Submit a UK deal to ShopAt.' That immediately separates it from read-side siblings such as get_deal, search_deals, hot_deals and my_submissions without needing to open any schema.

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

Usage Guidelines4/5

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

Gives strong eligibility conditions for when this is the right call: UK-only, GBP, direct https product URL on a UK retailer, honest current/was prices, no spam, and an approved agent credential. It never explicitly names an alternative tool (e.g. my_submissions for checking status, link_boundproof_identity for the credential path), so there is context but no stated exclusions.

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