Skip to main content
Glama

Dealio: Belgian deals

search_deals

Read-onlyIdempotent

Search the current promotions at Belgian retailers by product, brand or store, with optional filters. Returns the best matches (biggest per-item discount first unless sorted otherwise), each with price, discount, validity and a link to open it.

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
sortNoDefault: relevance when there is a query, else discount.
limitNoResults to return (default 10).
queryNoWords from the product, brand or kind of promotion, e.g. 'koffiecapsules', 'Philips', '1+1 gratis'. Optional.
storeNoStore name or slug, e.g. 'bol', 'Colruyt', 'albertheijn'. See list_stores. Optional.
offsetNoSkip this many results (for the next page).
categoryNoCategory slug or name: voeding, drank, verzorging, huishouden, baby, dier, elektronica, huis-tuin, mode, speelgoed, sport.
max_priceNoMaximum price per item in euro.
min_discountNoMinimum discount per item, in percent.
ends_within_daysNoOnly promotions that end within this many days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive search. The description adds useful behavioral context by stating that results are best matches and by listing returned fields such as price, discount, validity, and a link. The default-sort phrasing is slightly less precise than the schema's query-dependent default, but overall transparency is good.

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?

The definition is two sentences, front-loaded with the core action and scope, and every clause contributes useful information. There is no filler or repetition.

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 search tool with nine optional parameters, full schema coverage, and rich annotations, the description provides enough context to use it correctly. It also compensates for the lack of an output schema by naming the key return fields, though it does not mention pagination or the query-dependent default sort.

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%, so all nine parameters are already documented in the input schema. The description adds only high-level meaning such as searching by product, brand, or store and mentions optional filters, without adding syntax or format details beyond the schema.

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 description gives a clear verb and resource: searching current promotions at Belgian retailers by product, brand, or store. It is easy to distinguish from a single-deal fetch, but it does not explicitly name or contrast with sibling tools such as get_deal or list_stores.

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?

The description implies when to use the tool by stating it searches current promotions with optional filters, but it provides no explicit when-to-use guidance, prerequisites, or alternatives. The schema mentions list_stores for store lookup, but the description itself does not route the agent to sibling tools.

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