Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_order_detail

Read-onlyIdempotent

Retrieve a specific Ozon order by URL or orderId to view delivery details, items, and available actions; read-only, and works even if overview cards lack product links or names.

Instructions

Прочитать конкретный заказ, доставку, товары и доступные действия. Передайте url ИЛИ orderId из ozon_orders, даже когда карточка обзора не показала ссылку/названия товаров. Заказ не изменяется.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ozon_order_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
orderIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

The read-only profile is already carried by readOnlyHint/idempotent/destructive, and "Заказ не изменяется" largely restates it. The real added value is the return scope — the call surfaces delivery, products and available actions — which matters because there is no output schema. It does not cover failure modes or what happens with an invalid url, so a 4 rather than a 5.

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 sentences with the read scope front-loaded, then the parameter rule, then the safety note. Nothing is padded and the redundant safety line is one short clause.

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 two-parameter, read-only tool with no output schema, the description tells the agent what to pass, where to get it, and what data comes back. It is slightly thin on edge cases such as an unresolvable url, but nothing critical is missing for a correct invocation.

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 has to compensate, and it does: it states url and orderId are alternatives (ИЛИ), that either comes from ozon_orders, and that neither is mandatory to try. The exact orderId pattern lives only in the schema, but the semantic relationship between the two parameters is supplied by the text.

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?

"Прочитать конкретный заказ, доставку, товары и доступные действия" gives a specific verb (read) plus the resource and the exact payload scope (order, delivery, products, actions), which separates the detail tool from the list-oriented ozon_orders. It stops short of naming ozon_orders as the alternative for listing, so it is clear but not maximally differentiated.

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?

"Передайте url ИЛИ orderId из ozon_orders" establishes the precondition and the identifier source, and "даже когда карточка обзора не показала ссылку/названия товаров" tells the agent it is still usable when the overview is sparse. No explicit when-not-to-use or excluded cases are stated, which keeps it below a 5.

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