marketplaces-mcp-ru

Overview Schema Source Related Servers Discussions Admin

ozon_add_cabinet

Idempotent

Add or update an Ozon API cabinet by providing client_id and api_key. Requires explicit confirmation because credentials appear in chat; saved locally to ~/.marketplace-mcp/cabinets.json.

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.

Addedv0.5.2Sep 10, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: the key enters the chat transcript, persistence location (~/.marketplace-mcp/cabinets.json), file permissions (chmod 600), the 'never echoed' guarantee, and the default-name fallback behavior. This is rich, non-obvious context.

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 front-loaded with the tool's purpose and critical safety caveat, then organized into clear argument definitions. The formatting is scannable and every sentence adds information needed to invoke the tool correctly.

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 credential-storing operation, the description covers purpose, safety risks, parameters, storage location, and side effects. The output schema exists separately, so return values need not be described here. Nothing essential is missing for correct invocation.

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 description coverage is 0%, so the description carries the full parameter burden. It explains the expected credentials dict format for both Ozon and WB, the optional name behavior, and the required safety flag. This goes well beyond the bare schema.

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 states a specific action ('Add or update a cabinet') and clarifies the resource: a named set of API credentials. The 'from chat' context and the credential examples make the tool's role unmistakable even among many sibling tools.

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 explains when this tool is appropriate ('from chat') and warns that the key becomes part of the conversation. It also names the safer alternative (install.py / double-click installer) for cases where the key should not enter chat.

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

Deploy Server