Skip to main content
Glama

Today's deals and coupons

deals
Read-onlyIdempotent

action: daily = biggest verified price drops of the last 24 h at rated shops; coupons = valid coupon codes and promotions of compared shops.

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": {
      "action": "<action>"
    },
    "name": "deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows
actionYesOperation to run; help {topic:"deals"} lists each one's arguments
detailNocompact (default) or full
offsetNoRows to skip
countryNoCountry code, e.g. CZ
categoryNoCategory slug (daily)
min_percentNoMin discount in %

Output Schema

NameRequiredDescriptionDefault
moreNoHow to fetch the next page
limitNo
totalNoAll matches, not just this page
offsetNo
returnedNo
cross_border_noteNo
commission_disclosureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"Operation to run; help {topic:\"deals\"} lists each one's arguments"
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "compact (default) or full",
      +  "enum": [
      +    "compact",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip",
      +  "type": "number"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "commission_disclosure": {
      +      "type": "string"
      +    },
      +    "cross_border_note": {
      +      "type": "string"
      +    },
      +    "limit": {
      +      "type": "number"
      +    },
      +    "more": {
      +      "description": "How to fetch the next page",
      +      "type": "string"
      +    },
      +    "offset": {
      +      "type": "number"
      +    },
      +    "returned": {
      +      "type": "number"
      +    },
      +    "total": {
      +      "description": "All matches, not just this page",
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish this as a safe, read-only, idempotent, non-open-world operation, so the description's burden is lower. It adds useful behavioral context — the 24-hour recency window and the 'verified' qualifier on price drops, plus validity of coupon codes — but says nothing about pagination behavior, result ordering, or what happens when filters match nothing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with no filler, front-loading the action split so an agent can decide its mode immediately. It could be marginally improved with a leading clause naming the tool's purpose, but nothing in it is wasted.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. For a two-mode read tool with fully documented parameters, explaining what each action yields is sufficient; only filter interaction across modes (e.g. that category applies to daily) is left unstated.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description earns above baseline by giving real semantics to the required 'action' enum values, which the schema only labels as 'Operation to run'. The remaining parameters (country, category, min_percent, detail, limit, offset) are left entirely to 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 defines both operations concretely: 'daily' returns the biggest verified price drops of the last 24 h at rated shops, and 'coupons' returns valid coupon codes and promotions of compared shops. That is a specific resource plus scope for each mode. It does not explicitly contrast itself with siblings like price_watch or search, so it stops short of a 5.

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?

It implicitly tells the agent which action to pick when it wants deals versus coupons, which is genuine within-tool routing guidance. However, there is no explicit statement of when to use this tool instead of search, product, or price_watch, and no prerequisites or exclusions are given.

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