Skip to main content
Glama
serbia-prices-mcp

serbia-prices-mcp

by moskrc

Get Price History

get_price_history
Read-only

Retrieve a product's price history by EAN from Serbian retail price lists, including monthly snapshots and the current list, to compare prices over time.

Instructions

Price history of a product by EAN from the price lists on data.gov.rs: monthly snapshots published by the chains (snapshot='monthly') and today's list (snapshot='current').

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": {
      "ean": "<ean>"
    },
    "name": "get_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
eanYesEAN barcode from search results.
limitNoPage size.
offsetNoNumber of results to skip.
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.5/5.0
Behavior3/5

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

readOnlyHint=true already establishes this is a safe read. The description usefully adds the provenance and nature of the data (monthly chain-published snapshots plus today's list), which the annotations cannot convey. It says nothing about ordering of the returned history, how monthly snapshots relate to current data, currency handling, or pagination behavior, so meaningful behavioral gaps remain.

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 front-loaded sentence identifies the resource, the key, and the source without filler. The trailing parenthetical is the only part that does not earn its place, since it describes a mode the schema does not accept.

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?

With an output schema present and readOnlyHint supplied, the description need not describe return values, and it covers source and data vintage adequately for a simple lookup tool. The remaining gap is the unexplained snapshot distinction and whether both datasets are merged or selectable.

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 the baseline is 3; the description does not explain limit, offset, or retail_chains beyond what the schema states. It also references a 'snapshot' value that is absent from the four declared parameters, which adds ambiguity rather than meaning for the actual inputs.

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 (price history of a product keyed by EAN) and its data source (data.gov.rs price lists), which separates it from siblings like search_products or get_top_discounts. It loses a point because the parenthetical about snapshot='monthly' vs snapshot='current' implies a selectable mode that no parameter in the schema exposes, leaving the agent slightly unsure what the tool actually returns.

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 only implied: the schema says EAN comes 'from search results', so an agent can infer this is a follow-up to search_products for a known product. There is no explicit statement of when to prefer this over siblings, no when-not guidance, and no note on cost or call volume.

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