Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_review_prepare

Prepare an Ozon product review from owner-provided stars, text, pros, cons, and media, then return a preview and confirmation without publishing.

Instructions

Подготовить отзыв только по купленному товару: точные stars/text/pros/cons/media владельца. Не выдумывать опыт и НЕ публиковать. Вернуть preview и confirmation.

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": {
      "orderUrl": "<orderUrl>",
      "productTitle": "<productTitle>",
      "stars": "<stars>",
      "text": "<text>"
    },
    "name": "ozon_review_prepare"
  }
}

Input Schema

NameRequiredDescriptionDefault
consNo
prosNo
textYes
starsYes
mediaIdsNo
orderUrlYes
productTitleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent, open-world call, and the description adds the crucial facts that no publication happens and that the response is a preview plus a confirmation handle — effectively standing in for a missing output schema. It does not explain where the draft is persisted or how long the confirmation stays valid.

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?

Three short clauses, front-loaded with the main action, then the integrity constraint, then the return value. No filler and no repetition of the name.

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 7-parameter mutation-adjacent tool with no output schema and zero schema descriptions, the description covers the intent and the preview/confirm contract well but leaves the semantics of the required orderUrl and productTitle unexplained. An agent could still call it, but must guess how to identify the purchase.

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 description coverage is 0%, so the description carries the burden, and it names five of the seven fields (stars, text, pros, cons, media) with the intent that they reflect the owner's real experience. The two required fields orderUrl and productTitle are only obliquely implied by 'purchased product' and are never explained.

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?

Specific verb+resource (prepare a review) with an explicit scope restriction ('only for a purchased product') and an explicit non-goal ('do NOT publish'). It implicitly separates itself from the confirm/action siblings by framing this as a preview step, though it never names ozon_action_confirm outright.

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 clear use condition (only for already-purchased items) and an anti-hallucination rule plus a 'do not publish' boundary, which tells the agent this is a staging call. It stops short of naming the follow-up tool or stating what to do after obtaining the confirmation token.

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