Skip to main content
Glama

Dealectics deal verdict

Find current deals for a need

search_deals
Read-onlyIdempotent

Use when someone wants to buy something, precise or vague ('noise-cancelling headphones under 200 €', 'a gift for a DIY dad'). Returns at most five offers seen in the last three days in France or Germany, each with price, merchant link when known, separate relevance, deal-quality and purchase-feasibility signals, and its unknowns; or 'no_offer' with the reason. max_price, ship_to and exclude are hard limits. Offers marked 'lead' are real but unconfirmed: check the merchant page before presenting them as available. Each offer has a merchant_link status: 'resolved' (merchant_url is the product page), 'pending' (being looked up: repeat the same search after retry_after_seconds, once), 'abandoned' with a reason (no lookup is under way: use merchant_search_url) or 'unknown'. merchant_market is the country of the shop and cross_border is true when it differs from ship_to: delivery there is then unverified. delivery gives the shipping cost the listing stated, not a quote for an address. id identifies the same offer across calls. The merchant's live price is never rechecked: purchase_feasibility stays below 1.0 and every limit on it is named in unknowns. 'no_offer' comes with the limits applied and why recent candidates were left out. A 'no_offer' answer may carry 'alternatives': at most two offers of the same product type, inside the same limits. An alternative is not what was asked: say so to the person, with what 'differs' lists (an 'observed' of null means unknown, not identical).

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": {
      "query": "<query>"
    },
    "name": "search_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat the buyer wants, as said.
excludeNoWords an offer must not contain.
ship_toNoDelivery country, ISO 3166-1 alpha-2.
currencyNoCurrency of the ceiling. Only EUR is served.EUR
max_priceNoHard ceiling in euros. Never exceeded.
price_includes_shippingNoTrue when the ceiling must cover delivery too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / currency / description
      Added value: +"Currency of the ceiling. Only EUR is served."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (read-only, open-world, idempotent), it discloses the freshness window (three days), geographic corpus (FR/DE), the five-offer cap, that 'id' is stable across calls, and the critical caveat that the merchant's live price is never rechecked so purchase_feasibility stays below 1.0. It also enumerates every merchant_link status and its required reaction, and explains what a 'no_offer' response contains and that 'alternatives' are never what was asked.

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 trigger and the return shape before the edge cases, and nearly every sentence carries operational semantics an agent needs. The weakness is density: one unbroken block with deeply nested clauses such as the merchant_link status enumeration would be far easier to parse as a list.

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?

For a complex search tool with no output schema, the description fully documents the return contract: per-offer fields, three separate signals, the unknowns channel, the status machine for merchant_link, cross-border and delivery-caveat semantics, and the shape of both 'no_offer' and 'alternatives'. Nothing an agent needs in order to call it and interpret the result 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 100%, so the baseline is 3, but the description adds real meaning by classifying max_price, ship_to and exclude together as hard limits — the schema describes ship_to only as a delivery country, not as a hard filter. The price_includes_shipping interaction with the ceiling is left to the schema rather than elaborated, but the hard-limit framing lifts this above baseline.

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 opening sentence names the trigger ('someone wants to buy something') and the resource (offers/deals) with concrete examples of precise and vague queries, plus the return cap of five offers from the last three days in France or Germany. Sibling differentiation is implicit rather than stated: it never contrasts itself with price_verdict or create_watch, so an agent must infer that this is the discovery step that feeds those tools.

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?

It gives a clear when-to-use trigger with worked examples and prescribes operational follow-ups: retry once after retry_after_seconds on a 'pending' lookup, fall back to merchant_search_url on 'abandoned', and verify 'lead' offers before presenting them. It stops short of naming explicit when-not conditions or routing to a sibling when the buyer already has a watch.

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