Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_shopping_list

Create or verify a personal Ozon shopping list from product URLs and optionally save it after SKU and privacy checks; repeat calls do not duplicate a ready list.

Instructions

Создать или сверить личный лист покупок без обложки: name и productUrls. apply=true выполняет разрешённое сохранение с проверкой каждого SKU и приватности. При неизвестном исходе сначала collections с name. Повторный вызов не дублирует готовый список.

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": {
      "name": "<name>",
      "productUrls": "<productUrls>"
    },
    "name": "ozon_shopping_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
applyNo
descriptionNo
productUrlsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already say write, open-world, non-destructive, and not idempotent, yet the description still adds substance: apply=true is the committing path, each SKU and privacy are validated, and there is a recovery route via 'collections' when the outcome is unknown. The claim that a repeat call 'не дублирует готовый список' sits in mild tension with idempotentHint=false, but it reads as a dedup/verification guarantee for an already-existing list rather than a contradiction.

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?

Four short, front-loaded sentences with no filler: purpose first, then the apply semantics, then the recovery path, then the duplicate-safety note. The telegraphic style ('При неизвестном исходе сначала collections с name') is dense but each sentence carries a distinct instruction.

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 4-parameter write tool with no output schema, the definition covers the risky parts an agent needs: what apply commits, that validation happens per SKU, and how to recover from an ambiguous result. The gaps are the unexplained 'description' field and no hint about what a dry-run returns.

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 coverage is 0%, so the description must carry parameter meaning, and it only covers three of four: name, productUrls, and the apply flag (including its default-off dry-run semantics). The 'description' parameter is never mentioned, and there is no guidance on URL format, uniqueness expectations, or the 100-item cap.

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 opening states a specific verb pair and resource: 'Создать или сверить личный лист покупок без обложки' (create or reconcile a personal shopping list without a cover), and names the driving fields name and productUrls. It is clearly a write/verify tool for personal lists, though it never explicitly contrasts itself with the closest sibling, ozon_collection_create.

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 gives real operational guidance: apply=true performs the actual save, and on an unknown outcome the agent should consult 'collections' with the same name first, which implies apply=false is the safe pre-check. What is missing is any statement of when NOT to use it (e.g. when the target is a public collection rather than a personal list).

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