Skip to main content
Glama

Search products on sale

search_products
Read-onlyIdempotent

Find individual products currently on sale by keyword, optionally with a maximum price, currency and country. Returns up to 10 products with sale price, regular price, ship-to countries and links, and says when there are more. Covers products on sale, not coupon codes.

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_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesProduct keywords, e.g. "running shoes"
countryNoISO country code, e.g. CH or US. Returns offers for that country plus worldwide ones.
currencyNoISO currency, e.g. USD, EUR, CHF
max_priceNoMaximum price

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 establish read-only, idempotent, non-destructive behavior, and the description adds genuinely new facts: a hard cap of 10 results, the returned fields (sale price, regular price, ship-to countries, links), and the presence of a more-results indicator. It does not explain how to retrieve further pages, which is the one behavioral gap.

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, front-loaded with purpose and followed by return-shape and scope boundary. Every clause carries information; nothing is redundant with the title or schema.

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?

With no output schema, the description usefully summarizes the return payload and result cap, which is what an agent needs to plan calls. The only shortfall is not saying how to obtain additional results once the more-indicator appears, and there is no pagination parameter in the schema to reference.

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%, with formats (ISO codes, keyword example) already documented in the schema, so the baseline is 3. The description only restates that max price, currency and country are optional filters, adding little meaning beyond the field-level 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?

States a specific verb and resource ("Find individual products currently on sale") plus the filter dimensions, and explicitly carves out what it does not cover ("not coupon codes"), which distinguishes it from the search_coupons sibling without needing its 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?

Gives a clear use condition (keyword search for discounted products) and an explicit exclusion (coupon codes), which implicitly routes the agent to search_coupons. It stops short of naming that sibling or saying when search_stores/get_store_offers would be preferable, so the alternatives are implied rather than spelled out.

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.