Skip to main content
Glama

deals

by com.kitsdeals

Search live deals

search_deals
Read-only

Search live, human-reviewed deals by keyword. Matching is token-AND over product name, brand, category, and merchant. Returns up to 5 active deals (best score first) with price, discount, condition, merchant, product URL, and a server-verified human_summary sentence. Zero matches is a normal result for time-scarce inventory; the response then includes a no_match block describing the register_watch alternative.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 5).
queryYesSearch keywords — product name, brand, model number, or merchant. Token-AND: every word must match.
categoryNoCategory filter (comma-separated allowed). Currently in scope: electronics.
max_price_centsNoOnly deals at or below this price, in cents (e.g. 35000 = $350).
min_discount_pctNoOnly deals with at least this discount percentage.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations indicate a read-only operation, and the description adds significant behavioral detail: token-AND matching, a limited result set of up to 5 active deals, specific return fields, and a no_match block. No contradictions with annotations.

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?

Two sentences that are front-loaded with essential details: the core function and matching logic in the first, and important edge-case behavior in the second. No wasted words.

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?

Given no output schema, the description covers all critical aspects: input query, matching, result fields (price, discount, condition, merchant, URL, human_summary), limit, and the no-match fallback. It is comprehensive for the tool's complexity.

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

Parameters5/5

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

Schema coverage is 100%, and the description adds value by explaining the token-AND matching logic for the query parameter and the default limit of 5. It also clarifies the scope of matching fields, going beyond schema descriptions.

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 specifies a clear action: search live, human-reviewed deals by keyword. It details the matching method (token-AND over product name, brand, category, and merchant) and what is returned, making it distinct from sibling tools like get_deal or register_watch.

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 explains when to use (searching deals) and handles the zero-match case by directing to register_watch. However, it does not explicitly differentiate from other search-related siblings like latest_deals, leaving some ambiguity.

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

All deals toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool maps to a distinct operation: discovery (get_deal, latest_deals, search_deals), watch lifecycle (register_watch, check_watch, cancel_watch), and feedback (report_outcome). The potential overlap between latest_deals and search_deals is resolved by their freshness/curation vs keyword-search framing. No two tools appear to do the same thing.

Naming Consistency4/5

Six of seven tools follow a clear verb_noun pattern (register_watch, check_watch, cancel_watch, get_deal, search_deals, report_outcome). 'latest_deals' breaks the pattern by using an adjective_noun noun phrase instead of a verb, but this is a minor deviation. Overall the convention is predictable.

Tool Count5/5

Seven tools is well-scoped for a deals discovery and watch-monitoring server. Each tool covers a distinct need and none feel redundant. This is within the ideal range and not bloated.

Completeness4/5

The core lifecycle is covered: discover deals, get details, register a watch, check its status, cancel it, and report outcomes. Missing a list/update watch operation is a minor gap, but cancel-and-re-register works as a workaround. For the stated purpose, no severe dead ends exist.

Resources