Skip to main content
Glama

Heartly Deals — Live Flash Sales (Shopify & WooCommerce)

Search deals by category

search_deals_by_category

Search active deals filtered by category. The category argument is required. Other filters (country, min_discount_pct, ending_within_hours) are optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoISO 3166-1 alpha-2 country code. Filters to merchants whose shipping_countries include this code, plus merchants who ship worldwide.
categoryYesTop-level product category, e.g. "fashion", "beauty", "electronics".
min_discount_pctNoMinimum discount percentage. Only return deals at or above this value.
ending_within_hoursNoOnly return deals ending within this many hours from now.

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only states 'Search active deals' without disclosing behavior like rate limits, result ordering, pagination, or what 'active' means. Minimal transparency.

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, no fluff, front-loaded with action and required filter. Clearly structured.

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

Completeness3/5

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

Schema is rich, but description lacks context on return behavior, pagination, or what 'active' implies. No output schema exists, so description should cover more. Adequate but not thorough.

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 100% with detailed parameter descriptions. Description adds minimal value beyond stating category is required and others optional, which is already in schema. Baseline 3 holds.

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?

Clearly states verb 'search' and resource 'active deals' with filter by category. Distinguishes from siblings: get_deal_by_id is single deal, list_active_deals is unfiltered.

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

Usage Guidelines3/5

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

States required argument and optional filters, but does not explicitly describe when to use this tool vs alternatives. Could mention that list_active_deals is for unfiltered listing.

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.

TDQS

A4/5.0
Disambiguation5/5

Each tool has a distinct purpose: get by ID, list all active deals, and search by category. No overlap.

Naming Consistency5/5

All tools use consistent verb_noun snake_case: get_deal_by_id, list_active_deals, search_deals_by_category.

Tool Count5/5

3 tools is appropriate for a focused deals lookup server. Not too few or too many.

Completeness4/5

Covers key read operations for active deals, but missing merchant-specific or historical deals. Minor gap.

Resources