Skip to main content
Glama

Compare Prices Across Russian Marketplaces

compare_prices
Read-onlyIdempotent

Price one product across configured Russian marketplaces at once, returning a ranked offer list and per-source availability report.

Instructions

Price one product across every configured Russian marketplace at once.

Queries each marketplace concurrently and returns a single list ranked by price, plus a per-source report of what answered and what did not. This is the tool for "where is X cheapest" — running the per-marketplace search tools one at a time gives the same data far more slowly and without the ranking.

Two things to read carefully in the output:

  • cheapest is chosen on everyday prices. Yandex Market's conditional price appears as price_with_subscription_rub and is deliberately excluded from ranking: it needs paying with Yandex Pay (earlier Yandex Plus).

  • source_outcomes shows which marketplaces answered. A blocked or timed-out source means the comparison is partial, not that the product is absent there — complete tells you which case you are in.

Titles are matched loosely: marketplaces name things differently, so scan the results rather than assuming every row is the identical model. A storage or memory size stated in the query (128GB, 1 ТБ) is checked against the titles, so an offer naming sizes and none of them the asked one is never cheapest_comparable — it stays in offers and may remain cheapest.

Full field list and error codes: guide://compare/compare_prices.

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": {
      "query": "<query>"
    },
    "name": "compare_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to price, in Russian — e.g. 'стиральная машина узкая' or 'iphone 15 128'.
sourcesNoRestrict to specific marketplaces (wildberries, ozon, yandex_market, avito, taobao, megamarket, lamoda, dns, citilink, aliexpress). Omit to query all.
in_stock_onlyNoRank only offers whose marketplace explicitly reports them in stock.
per_source_limitNoHow many offers to take from each marketplace.

Output Schema

NameRequiredDescriptionDefault
queryNo
offersNo
cheapestNo
completeNo
warningsNo
sources_okNo
total_offersNo
server_versionNo
source_outcomesNo
sources_queriedNo
price_spread_rubNo
cheapest_comparableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.9.4
    • changedInput schema / properties / sources / description
      Previous value: -"Restrict to specific marketplaces (wildberries, yandex_market, ozon). Omit to query all."New value: +"Restrict to specific marketplaces (wildberries, ozon, yandex_market, avito, taobao, megamarket, lamoda, dns, citilink, aliexpress). Omit to query all."
  2. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / in_stock_only
      Added value: +{
      +  "default": false,
      +  "description": "Rank only offers whose marketplace explicitly reports them in stock.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / cheapest_comparable
      Added value: +{}
  3. First observedv1.5.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds genuinely new behavior: concurrent querying, a partial-result model where a blocked source is not evidence of absence (with `complete` and `source_outcomes` to disambiguate), and a ranking rule that deliberately excludes Yandex Market's subscription price. This is exactly the kind of operational nuance annotations cannot carry.

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 one-sentence purpose, then the ranking/latency argument, then a short bullet block on output pitfalls. Dense and mostly earning its space, though the two-bullet block plus the size-matching paragraph make it longer than strictly required for an agent that also has an output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter, parallel-fanout, open-world tool, the description covers the failure mode that matters most (partial coverage), the ranking semantics, and the loose-matching caveat, and it points to `guide://compare/compare_prices` for the full field list and error codes. An output schema exists, so omitting return-value detail is correct.

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 adds real meaning to `query`: a size token present in the query (128GB, 1 ТБ) is enforced against titles, so an offer naming different sizes cannot become `cheapest_comparable`. The remaining three parameters are left entirely to the schema, which is why this is not a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb, resource, and scope: price one product across every configured Russian marketplace, returning a list ranked by price. It explicitly separates itself from the per-marketplace search tools, so an agent can pick it without opening any schema.

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 a concrete selection rule — "the tool for 'where is X cheapest'" — and names the alternative it replaces (running per-marketplace search tools one at a time) along with why it is worse (slower, no ranking). It does not cover the other comparison-family siblings or say when not to reach for it, so it stops short of fully explicit routing.

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