Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_search

Read-onlyIdempotent

Search Ozon products by query, then filter and sort results by price, brand, delivery time, rating, and attributes to compare offers and find items matching your shopping needs.

Instructions

Поиск с ценой Ozon Карты, рейтингом товара, числом отзывов/вопросов и сроком доставки. sort: popular/cheaper/expensive/rating/new/relevance. Фильтры: цена, brands, deliveryWithinDays и динамические name/values из ozon_search_filters. Неподтверждённые ограничения не игнорируются.

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

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNo
queryYes
brandsNo
filtersNo
maxPriceRubNo
minPriceRubNo
deliveryWithinDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds the shape of returned data (card price, rating, review counts, delivery time), which is genuinely beyond annotations. It omits result-count limits (max 30), pagination behavior, and the meaning of 'unconfirmed restrictions', which is too cryptic to inform behavior.

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?

It is front-loaded with the returned data and then the sort/filter surface in two dense clauses, with no filler. The final sentence about unconfirmed restrictions is opaque enough that it arguably fails to earn its space, but overall the text is tight.

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?

For a read-only search with no output schema, the description adequately covers what comes back and how sort/filters work, which is the core of correct invocation. It falls short on pagination/limit semantics and price units, gaps an agent would notice on a tool with 8 parameters at 0% schema coverage.

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 0%, so the description must carry parameter meaning; it does cover sort, price bounds, brands, deliveryWithinDays, and the dynamic filters array, and points to ozon_search_filters for valid name/values. It says nothing about query, limit (including its 1–30 range), or that prices are in rubles, leaving several of the 8 parameters undocumented in both places.

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 concrete verb (search) and enumerates the payload the agent gets back: Ozon Card price, rating, review/question counts, and delivery time. It distinguishes itself from the sibling ozon_search_filters by redirecting filter discovery there. It never states explicitly what resource is being searched (products), which keeps it from 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 Guidelines3/5

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

It gives one concrete routing rule: dynamic filter name/values come from ozon_search_filters, which is a real alternative and useful. However, it does not explain when an agent should prefer ozon_search over ozon_product or when to skip straight to a collection, and the closing sentence about 'unconfirmed restrictions' gives no actionable when-to-use condition.

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