Skip to main content
Glama
neuratechcompany-ops

Kettu Marketplace Intelligence

Compare Prices Across Russian Marketplaces

compare_prices
Read-onlyIdempotent

Compare prices across Russian marketplaces in one query, then get a price-ranked list and per-source status showing which marketplace has the product for less and whether all sources responded.

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 subscriber price appears as price_with_subscription_rub and is deliberately excluded from ranking, since it requires a paid Yandex Plus subscription.

  • 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.

Error Format

On validation failure, raises ToolError with a JSON message describing the error code and whether it is retryable. Individual source failures do NOT raise — they are reported in source_outcomes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesWhat to price, in Russian — e.g. 'стиральная машина узкая' or 'iphone 15 128'.
sourcesNoRestrict to specific marketplaces (wildberries, yandex_market, ozon). Omit to query all.
per_source_limitNoHow many offers to take from each marketplace.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoThe query that was priced.
offersNoAll offers, cheapest first. Offers without a price are kept at the end.
cheapestNoLowest everyday price found. None when no marketplace returned a price.
completeNoTrue only when every queried marketplace answered. False means the ranking is partial.
warningsNoConnector-level warnings (partial data, no prices).
sources_okNoMarketplaces that answered successfully.
total_offersNoTotal offers across all marketplaces.
server_versionNoConnector version.
source_outcomesNoPer-marketplace outcome, including failures — read this before trusting the ranking.
sources_queriedNoMarketplaces that were attempted.
price_spread_rubNoDifference between the highest and lowest everyday price — how much the choice is worth.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.2.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as read-only and idempotent, and the description adds substantial behavior beyond that: concurrent querying, per-source reporting, partial-result semantics when sources time out, exclusion of Yandex subscription pricing from ranking, and the guarantee that individual source failures do not raise errors. No contradiction with annotations.

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?

The description is well organized with clear sections, a front-loaded headline, and bolded caveats for important output fields. Every paragraph adds distinct information needed for correct interpretation, with no filler.

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?

The description covers output semantics (cheapest, price_with_subscription_rub, source_outcomes, complete), error format, loose title matching, and the concurrent behavior. The output schema can carry return-value details, so nothing critical is missing for an agent to call and interpret the result correctly.

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?

The input schema already documents all three parameters with 100% coverage, so the description does not need to repeat parameter details. The description focuses instead on output interpretation and ranking semantics, which is appropriate; baseline 3 applies.

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 and resource: 'Price one product across every configured Russian marketplace at once.' It also differentiates from per-marketplace search siblings by naming the ranking behavior and by framing the exact question it answers: 'where is X cheapest'.

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

Usage Guidelines5/5

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

Explicitly identifies when to use this tool: 'This is the tool for "where is X cheapest"'. It also contrasts with the alternative (running per-marketplace search tools one at a time) and explains that the alternative is slower and lacks ranking.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/neuratechcompany-ops/kettu-marketplace-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server