Skip to main content
Glama

list_recently_reduced

Deals whose price was recently cut (1–40% drop between the two latest prices).

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": "list_recently_reduced"
  }
}

Input Schema

NameRequiredDescriptionDefault
countriesNoMarkets (default CZ)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / countries / items / enum
      Previous value: -[
      -  "CZ",
      -  "SK",
      -  "DE",
      -  "AT",
      -  "PL",
      -  "HU",
      -  "RO",
      -  "LT",
      -  "LV",
      -  "NO"
      -]New value: +[
      +  "CZ",
      +  "SK",
      +  "DE",
      +  "AT",
      +  "PL",
      +  "HU",
      +  "RO",
      +  "LT",
      +  "LV",
      +  "NO",
      +  "BG"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / countries / items / enum
      Previous value: -[
      -  "CZ",
      -  "SK",
      -  "DE",
      -  "AT",
      -  "PL",
      -  "HU",
      -  "RO",
      -  "LT",
      -  "LV"
      -]New value: +[
      +  "CZ",
      +  "SK",
      +  "DE",
      +  "AT",
      +  "PL",
      +  "HU",
      +  "RO",
      +  "LT",
      +  "LV",
      +  "NO"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / countries / items / enum
      Previous value: -[
      -  "CZ",
      -  "SK",
      -  "DE",
      -  "AT",
      -  "PL",
      -  "HU",
      -  "RO"
      -]New value: +[
      +  "CZ",
      +  "SK",
      +  "DE",
      +  "AT",
      +  "PL",
      +  "HU",
      +  "RO",
      +  "LT",
      +  "LV"
      +]
  4. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full load; it usefully defines the inclusion rule (1–40% drop across the two most recent prices), which is real behavioral detail beyond the schema. However, it says nothing about ordering, result limits, or whether deals outside the 1–40% band are excluded or merely deprioritized.

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?

A single short sentence, front-loaded with the key qualifying criterion and free of filler. Nothing is redundant or buried.

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?

For a simple one-optional-parameter read tool with no output schema, the core definition is adequate, but a user of the tool would still want to know the default market behavior and how results are ordered or capped. It is minimally sufficient rather than complete.

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% and the single optional 'countries' parameter is fully documented in the schema, so the baseline is 3. The description adds no market-scope context of its own (e.g., that results default to CZ).

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 names a specific resource (deals) and a precise qualifying condition: a 1–40% price drop between the two latest prices. It is unambiguous about what set is returned, though it doesn't explicitly distinguish itself from siblings like list_hot_deals or get_price_movers.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives such as list_hot_deals or get_price_movers, which sound overlapping. The qualifying threshold implies a use case, but the agent must infer it and cannot tell which sibling to prefer.

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