ozon-mcp-ru

Overview Schema Source Related Servers Score Discussions Admin

ozon_add_cabinet

Idempotent

Add or update an Ozon or WB cabinet's API credentials from chat; requires confirmation because the key enters the chat transcript.

Instructions

Add or update a cabinet (a named set of API credentials), from chat.

⚠️ This puts the key into the chat transcript — requires i_understand_key_goes_to_chat=true. The terminal-free safe alternative is the installer (install.py / double-click), where the key never enters chat.

Args: credentials: dict with the required fields for this service ({fields}). For Ozon: {{"client_id": "...", "api_key": "..."}}; for WB: {{"token": "..."}}. name: optional label. If omitted, the cabinet is named after the real shop name fetched from the marketplace (falls back to "main"). i_understand_key_goes_to_chat: must be true to proceed. Saved to ~/.marketplace-mcp/cabinets.json (local, chmod 600), never echoed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`credentials`	Yes
`i_understand_key_goes_to_chat`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.3Sep 11, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds critical context: the key enters the chat transcript, requires explicit acknowledgment, storage path (~/.marketplace-mcp/cabinets.json) with chmod 600, and that it is never echoed. This is substantial additional behavioral disclosure beyond annotations, with no contradictions.

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 well-structured: a clear purpose sentence, a prominent security warning, and a compact parameter list. It front-loads the most important info (security) and avoids redundancy. Each sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a security-sensitive credential-management tool, the description covers purpose, parameters, security implications, storage, and alternatives. Even without seeing the output schema, the description is self-sufficient for an agent to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description fully compensates. It explains the credentials format for Ozon and WB, the name parameter's fallback behavior, and the i_understand_key_goes_to_chat requirement. Every parameter is meaningfully described.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb (add/update) and resource (cabinet, a named set of API credentials), and specifies it operates from chat. It distinguishes from installer alternative and implies service scope (Ozon) by giving credential examples. This is specific and unambiguous.

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

Usage Guidelines5/5

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

It explicitly names the safe alternative (install.py / double-click) and the condition for using this tool (accepting that the key goes to chat). This provides clear when-to-use and when-not-to-use guidance, going beyond mere description.

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