Skip to main content
Glama
serbia-prices-mcp

serbia-prices-mcp

by moskrc

Search Products

search_products
Read-only

Search current product prices across Serbian retail chains by product name, synonyms, or EAN barcode. Compare exact items and store formats by price; retry with broader terms when no match is found.

Instructions

Search current product prices across Serbian chains. Pass the product name in Serbian Latin (translate from Russian/English first) and optionally synonyms as extra list items. Most relevant names first, then the cheapest shelf price (price of the package as sold). If nothing is found, retry with a synonym or a more general word. Pass ean instead of query to compare one exact product across all chains and store formats: results are sorted by price, diff_rsd and diff_pct show the difference from the cheapest.

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

Input Schema

NameRequiredDescriptionDefault
eanNoEAN barcode from earlier results: compare this exact product across all chains and formats.
limitNoPage size.
queryNoSerbian Latin product name plus optional synonyms, e.g. ['pileci file']. Not needed with ean.
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'].

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

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds genuine context beyond that: result ordering (relevance first, then cheapest shelf price), what diff_rsd and diff_pct mean, and the retry heuristic. It does not cover pagination behaviour or rate/volume limits on a 6-param search, so it is useful but not complete.

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?

Front-loaded with the core action, then the two access modes, then fallback advice — a sensible order with no filler. A couple of clauses are densely packed (sorting plus diff-field explanation in one sentence), but nothing is expendable.

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 re-explained, and the description still clarifies the two result shapes (name search vs EAN comparison). Across 6 parameters and a non-obvious language constraint, the missing pieces are pagination guidance and any tie to sibling tools.

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 3 baseline is met by the schema alone; the description adds real meaning on top by framing ean and query as alternative modes ('pass ean instead of query') and clarifying that the query list holds a Serbian Latin name plus optional synonyms. limit, offset, category and retail_chains get no treatment in the description, but their schema text is adequate.

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?

States a specific verb and resource — 'Search current product prices across Serbian chains' — with an explicit scope (current prices, Serbian market). It never names a sibling, so an agent must infer the boundary with get_price_history (historical) on its own, which keeps it 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 Guidelines4/5

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

Gives concrete routing within the tool: use query for a name search, pass ean instead to compare one exact product across chains, and retry with a synonym or broader word when nothing is found. It also states a prerequisite (translate to Serbian Latin first). It does not say when to prefer a sibling tool such as get_price_history or get_top_discounts, which is the remaining gap.

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