Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_cart_add

Adds a specified product and quantity to an existing Ozon cart while preserving other items. Use preview mode by default or set apply=true to execute; it does not place an order.

Instructions

Добавить конкретный товар в корзину с указанным количеством, сохраняя остальные позиции. apply=true — выполнить по поручению; иначе preview. Покупку не оформляет.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
applyNo
quantityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, and the description adds two useful facts beyond them: existing items are preserved and apply=false is a preview. However, it says nothing about authentication requirements, what preview actually returns, or whether repeating the same call duplicates the line item (relevant given idempotentHint=false).

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 no filler: the action and its non-destructive scoping come first, then the apply semantics, then the checkout exclusion. Every clause carries distinct information.

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 mutation tool with no output schema and zero parameter descriptions, the definition covers the risky part (preview versus execute) well. It falls short on how the product is identified via the required url and on what the preview result looks like, which are the remaining gaps an agent needs before calling it.

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% across three parameters, so the description must carry the load. It explains apply via the preview/execute distinction and implies quantity ('с указанным количеством'), but leaves the only required parameter, url, completely undefined — its expected format (product page URL versus an identifier) and the 1–20 quantity cap are not addressed.

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 gives a specific verb and resource in 'Добавить конкретный товар в корзину' and clarifies scope with 'сохраняя остальные позиции' (append rather than replace). It also distinguishes itself from checkout with 'Покупку не оформляет', so an agent can tell it apart from ozon_checkout_prepare, though it does not explicitly name the sibling cart-viewing tool.

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 explicitly defines the two execution modes: 'apply=true — выполнить по поручению; иначе preview', which tells the agent exactly when a real mutation occurs versus a dry run. It lacks any guidance on prerequisites (e.g. auth) or when to prefer ozon_cart or checkout, but the mode selection is unambiguous.

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