Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_product_variants

Read-onlyIdempotent

Retrieve observed product variant groups such as color, size, power, and configuration from an Ozon product URL, returning each variant’s variantId, URL/SKU, and availability state.

Instructions

Наблюдаемые группы вариантов товара: цвет, размер, мощность, комплектация. Возвращает варианты с variantId, URL/SKU и состоянием.

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

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior4/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 value beyond them by disclosing what is returned (variantId, URL/SKU, state) and, through the word 'Наблюдаемые' (observable), implying that only currently visible variants are listed — a useful behavioral nuance. It does not mention whether results are paginated or what happens when a product has no variants.

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 compact sentences, front-loaded with the resource and followed by the return shape; nothing is padded. It is slightly too terse for the amount of unexplained behavior (the url parameter, the 'observable' qualifier), which costs it the top score.

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?

With no output schema, the description usefully compensates by naming the returned fields, and the annotations handle safety. However, for a tool whose only input is an undescribed URL and which sits beside a select tool, the absence of both parameter explanation and usage/routing guidance leaves meaningful gaps.

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?

The single required parameter 'url' has 0% schema description coverage, and the description does not mention it at all — not the expected URL format, not whether it must be a product page URL versus a variant URL. With the schema silent, the description carries the full burden here and leaves it unmet.

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 states a concrete verb and resource: it returns product variant groups broken down by color, size, power, and configuration, and lists the fields each variant carries (variantId, URL/SKU, state). That is specific enough to distinguish it from a plain product lookup, though it never names the closely related sibling ozon_product_variant_select, so the boundary is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to call this rather than ozon_product or ozon_product_variant_select, and no stated prerequisites or follow-up steps. An agent must infer from the name alone that this is the discovery step preceding a variant selection.

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