Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_product

Read-onlyIdempotent

Fetch a complete Ozon product card by URL, including coupon status, Ozon Card price, rating, reviews, specs, seller, and delivery. Use sections to return only needed details.

Instructions

Полная карточка: купон (coupon: наличие/применение/цена уже со скидкой), название, подтверждённая цена Ozon Карты, рейтинг/отзывы/вопросы, раскрытое описание/характеристики, продавец и доставка. sections позволяет узкий запрос. Для галереи, полных отзывов и вопросов используйте отдельные инструменты.

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": {
      "url": "<url>"
    },
    "name": "ozon_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
sectionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/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 the safety profile is covered. The description adds useful scope disclosure — that reviews and questions here are summary-level only, with full content elsewhere. It says nothing about authentication needs (the Ozon Card price implies a logged-in session) or failure behavior for an invalid URL.

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?

Two sentences, information-dense, front-loaded with the returned payload before the routing advice. The parenthetical coupon detail is slightly noisy but earns its place by clarifying discounted-price semantics.

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?

There is no output schema, so the description carries the return-value burden — and it does so by enumerating the returned sections. For a read-only single-resource getter with only two parameters, the remaining gaps (url format, what an empty sections array means) are minor.

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 explains that 'sections' narrows the request, which adds semantics beyond the enum value names (summary/description/characteristics/seller/delivery), but it never mentions the required 'url' parameter at all — its format, that it is a product URL, or length constraints. Partial compensation only.

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 enumerates exactly what the tool returns — coupon state, name, confirmed Ozon Card price, rating/reviews/questions, description/characteristics, seller, delivery — making the resource unambiguous. It lacks an explicit verb (no 'returns'/'fetches'), but the enumerated payload makes the operation inferable. It distinguishes itself from ozon_product_media, ozon_reviews and ozon_questions by pointing those use cases elsewhere.

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?

It explicitly routes the agent away from this tool for gallery images, full reviews and questions, and explains that 'sections' enables a narrow request. The alternatives are described generically as 'separate tools' rather than named, but the conditions for use and non-use are clear.

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