ZoZoPeak: Verified Coupons & Deals MCP

Find Store Deals

find_store_deals

Read-onlyIdempotent

Looks up deals that need no code for one online store. Offers come from official affiliate-network feeds; each offer shows when it was last seen in its feed (null when the feed does not report it); offers past their listed end date are never returned. Badges mark TakeDeals-verified offers and official brand-program offers. Results are ranked verified first, then by stated saving, never by commission. Links may be affiliate links at no cost to the shopper. Use when the user asks about current offers at a named store. An empty list means no deal is listed right now.

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": {
      "store": "<store>"
    },
    "name": "find_store_deals"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Results to return, 1 to 10, default 5.
`store`	Yes	Store name, domain or any URL on the store, for example 'aliexpress.com'. Any spelling that names the store is matched to it.
`country`	No	Shopper's two-letter ISO country code such as US, GB or AE. Keeps offers valid for that country, including worldwide ones.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description is free to add the parts annotations cannot: provenance (official affiliate-network feeds), freshness semantics (last-seen timestamp, null when unreported), expiry filtering, ranking order (verified first, then stated saving, never commission), badge meanings, and affiliate-link disclosure. This is exactly the extra context an agent needs to trust and present results.

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?

It is front-loaded with the core action and the sentences are information-dense rather than repetitive. The middle section on badges and ranking is longer than strictly necessary for invocation, but every clause carries signal an agent uses when summarizing results.

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

Completeness5/5

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

There is no output schema, so the description carries the return-value burden and does so: it explains the last-seen field, null handling, expiry exclusion, badges, ranking, and the meaning of an empty list. Nothing an agent needs in order to call this correctly or narrate results is missing.

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%, so all three parameters (store, country, limit) are already documented in the schema and the baseline applies. The description adds no syntax or format detail about how store names or country codes are interpreted beyond what the schema states.

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?

"Looks up deals that need no code for one online store" gives a specific verb, a precise resource, and a scoping constraint (code-free, single store) that implicitly separates it from a coupon-code lookup. An agent can identify the operation without opening the 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?

"Use when the user asks about current offers at a named store" gives a clear triggering condition, and the empty-result sentence tells the agent how to interpret a null outcome. It stops short of naming the sibling find_coupons as the alternative for code-based discounts, so the when-not guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ZoZoPeak: Verified Coupons & Deals MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?