Skip to main content
Glama
serbia-prices-mcp

serbia-prices-mcp

by moskrc

Get Top Discounts

get_top_discounts
Read-only

Finds current grocery promotions in Serbian retail chains at or above a minimum discount percentage, flagging possibly inflated regular prices and discounts needing in-store verification.

Instructions

Current promotions with discount of at least min_discount_pct, as published by the chains. regular_raised_before_promo=true means the regular price was raised compared to the monthly snapshots of recent months, so the discount may be inflated; false does NOT confirm the discount is real. needs_verification=true marks discounts of 80% or more: usually clearance of leftover stock or a data error in the published price list; warn the user to check in the store.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size.
offsetNoNumber of results to skip.
categoryNoOptional category name or number 1-25.
retail_chainsNoOptional chain or store format names to restrict results, e.g. ['Lidl', 'Maxi', 'Idea'].
min_discount_pctNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
limitYes
totalYesNumber of items on all pages.
offsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, so the description carries the interpretive burden and does it well: it explains that regular_raised_before_promo=true means the discount may be inflated, explicitly warns that false does NOT confirm a real discount, and defines needs_verification as discounts of 80%+ that are usually clearance or data errors. This is exactly the caveat context an agent needs to avoid overstating a discount to a user.

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?

The core scope is front-loaded in the first clause, and the remaining two clauses are packed with caveat semantics rather than filler. The semicolon-chained sentences are dense but every clause carries decision-relevant meaning.

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 shape need not be described, and the description covers the derived-flag semantics that the schema would not explain. It is slightly thin on how the filters combine (e.g., whether retail_chains matching is exact or fuzzy), but nothing critical is missing for correct invocation.

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 80%, so limit, offset, category and retail_chains are already documented in the schema. The description adds value by giving semantics to the undocumented min_discount_pct (it is a floor on the discount) and by tying the 80% threshold to needs_verification, which the schema does not convey.

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 first clause names the resource (current promotions/discounts), the source (as published by the chains) and the threshold filter (at least min_discount_pct), so the agent knows exactly what it returns. It does not explicitly contrast itself with search_products or optimize_basket, so sibling differentiation is left implicit.

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?

Usage is implied by the discount-threshold framing, and the description instructs the agent to 'warn the user to check in the store' for needs_verification hits, which is downstream guidance rather than tool selection guidance. There is no statement of when to prefer this over search_products or optimize_basket, and no exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.