Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_action_status

Read-onlyIdempotent

Reads the status of a prepared or started final action, helping you verify unknown or attempting outcomes instead of resubmitting.

Instructions

Прочитать состояние подготовленного/начатого конечного действия. unknown/attempting требуют сверки факта, а не повторной отправки.

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": {
      "token": "<token>"
    },
    "name": "ozon_action_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, open-world, and non-destructive. The description adds useful behavioral nuance by warning that unknown/attempting states require fact verification rather than re-sending, though it does not describe return fields or the full set of possible states.

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?

The description is two short sentences with the purpose front-loaded and no wasted wording. The second sentence adds a specific state-handling rule rather than repeating structured data.

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 low-complexity read-only status tool with rich annotations, the description covers the basic purpose and one important state-handling case. It remains incomplete because the required token parameter is undocumented and the return states are only partially described, with no output schema to compensate.

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 schema has one required token parameter with 0% description coverage, and the description does not explain what the token represents or how it should be supplied. The parameter name is somewhat self-explanatory, but the description adds essentially no semantic information beyond the schema.

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 specific verb and resource: reading the state of a prepared or started final action. This is clearer than a tautology and broadly distinguishes status checking from a confirm-style sibling, though it does not explicitly name the alternative tool.

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?

It implies use when checking the state of a prepared or started action and gives handling guidance for unknown/attempting states, warning against resending. However, it does not explicitly say when to call this instead of ozon_action_confirm or other action-related tools.

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