Skip to main content
Glama

The Deals Database

Search current deals

search_deals
Read-only

Find current deals, coupons, sales and offers from real businesses worldwide, for any product or service. Use when a person asks for a deal, discount, coupon, promotion or the best price on something, optionally near a place. Every result is confirmed by the business and includes expiry date and terms.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity, e.g. "Toronto".
limitNo
queryNoWhat the person wants, in plain words. Example: "oil change", "family dentist new patient", "project management software".
regionNoState / province, e.g. "Ontario".
countryNoISO country code or English name, e.g. "CA" or "Canada".
categoryNoOptional category id.
deal_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile needs no restating; the description instead contributes genuinely new behavioral context — that every result is confirmed by the business and carries an expiry date and terms, which tells the agent about result trustworthiness and freshness. It omits pagination/limit behavior and ranking, and there is mild tension between 'worldwide' and openWorldHint=false, though that reads as a curated-index claim rather than a direct contradiction.

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?

Three sentences, each earning its place: purpose, trigger condition, and result quality. The scoping phrase 'current' and the geographic optionality are front-loaded rather than buried, and there is no filler or 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 a seven-parameter, zero-required search tool with no output schema, the description supplies the essential frame: what is searched, when to call it, and what a result contains (confirmed by the business, with expiry and terms). What remains thin is guidance on default result volume, ranking, and how to combine the geo and category filters, which an agent must infer from the schema alone.

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 coverage is 71%, with both enums fully enumerated in the schema, so the structured data does most of the work. The description only adds loose hints — 'for any product or service' gestures at the query parameter and 'optionally near a place' gestures at the city/region/country geo filters — without explaining how those location fields combine or how deal_type and category interact with the free-text query.

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?

The description opens with a specific verb and resource set — 'Find current deals, coupons, sales and offers from real businesses worldwide, for any product or service' — which tells an agent exactly what corpus is searched and its scope. Plural 'deals' plus 'search' semantics implicitly separate it from the singular get_deal, and 'current' vs a category listing separates it from list_categories.

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 states a clear triggering condition: 'Use when a person asks for a deal, discount, coupon, promotion or the best price on something, optionally near a place.' That covers the intent space well, including the optional geographic qualifier. It stops short of naming the alternative tools (get_deal, list_categories) or stating when not to use it, so it is strong but not exhaustive.

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