Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_cart

Read-onlyIdempotent

Reads the current Ozon cart to show item quantities, selections, Ozon Card prices, and delivery times without making changes.

Instructions

Прочитать корзину, количества/выбор, цены Ozon Карты и сроки доставки. Ничего не меняет.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'Ничего не меняет' largely restates structured data. What the description adds beyond that is the payload scope (quantities, card prices, delivery estimates), which is genuinely useful, but it says nothing about auth requirements, staleness of delivery estimates, or failure modes.

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?

A single compact sentence with the action front-loaded, then the returned data, then the read-only guarantee. No filler or redundancy.

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 parameterless read-only tool with no output schema, the description covers the essentials: what is fetched and that nothing is mutated. Minor gaps remain around whether a session/auth must already exist and how current the delivery and pricing figures are.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly does not invent arguments for a no-arg call.

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 plus resource: 'Прочитать корзину' (read the cart), extended with exactly what is surfaced – quantities/selection, Ozon Card prices, delivery times. The closing 'Ничего не меняет' implicitly separates it from the mutation sibling ozon_cart_add, though no sibling is named outright.

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

Usage Guidelines3/5

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

The read-only framing ('Ничего не меняет') implies this is the inspection path rather than the add/checkout path, so usage is inferable. There is no explicit statement of when to prefer it over ozon_cart_add or ozon_checkout_prepare, and no preconditions such as authentication.

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