Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_questions

Read-onlyIdempotent

Retrieve Ozon product questions with all revealed answers, including author, date, and seller flag, using limit/cursor pagination without sending new questions.

Instructions

Отдельные вопросы и все раскрытые ответы, с автором/датой/признаком продавца. Поддерживает limit/cursor; не отправляет новых вопросов.

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_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
limitNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact: only 'раскрытые' (revealed/unhidden) answers are returned, which affects what the agent can expect in results. It restates the read-only nature, which is redundant but harmless.

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 short clauses, front-loaded with what is returned, followed by the pagination note and the negative constraint. No filler or repetition. It could be tightened only marginally.

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

Completeness3/5

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

For a simple read-only retrieval tool with full annotation coverage and no output schema, the description gives an adequate sketch of return content and pagination. It falls short on the required 'url' parameter and on any indication of result volume or ordering, which an agent would need to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 the parameter burden. It mentions limit/cursor support, which at least signals the pagination contract, but it never explains what 'url' — the single required parameter — should contain, nor the 1-50 range on limit or the cursor format.

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 — individual questions together with all revealed answers — plus the fields returned (author, date, seller flag). That is a clear verb-less but concrete retrieval purpose. It does not explicitly distinguish itself from the sibling ozon_reviews, which is the main gap keeping it below 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?

The clause 'не отправляет новых вопросов' implicitly tells the agent this is a read path and not a posting path, which is useful routing information. However, there is no explicit statement of when to pick this over ozon_reviews or ozon_review_prepare, so the usage guidance remains implied rather than stated.

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