moysklad-mcp-ru

Overview Schema Source Related Servers Discussions Admin

ms_add_cabinet

Idempotent

Add or update a cabinet (named set of marketplace API credentials) directly from chat. Requires explicit user confirmation that the key will be placed in 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.1.0Jul 4, 2026

TDQS

A5/5.0

Behavior5/5

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

The description goes far beyond annotations by disclosing the security-critical behavior: the key ends up in the chat transcript, the data is saved to ~/.marketplace-mcp/cabinets.json with chmod 600, and the key is never echoed. It also clarifies the upsert nature with 'Add or update,' aligning with the idempotentHint.

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 compact and well-organized, with the purpose and critical warning front-loaded, followed by a structured Args section. Every sentence adds operational or safety value, and the file path/permissions detail is not padding.

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?

Despite having an output schema, the description covers all operational context an agent needs: storage location, permissions, naming fallback, service-specific credential shapes, and the safety gate. 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%, but the description compensates by fully documenting all three parameters: credentials object with service-specific examples for Ozon and WB, optional name with fallback behavior, and the required i_understand_key_goes_to_chat boolean. This meaningfully exceeds what the bare schema provides.

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 opens with a specific verb and resource: 'Add or update a cabinet (a named set of API credentials), from chat.' It clearly names the operation, the resource type, and the interaction context, and it cannot be confused with sibling tools like ms_list_cabinets, ms_use_cabinet, or ms_remove_cabinet.

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 states when to use this tool (from chat) and contrasts it with the terminal-free installer alternative where 'the key never enters chat.' It also documents the required consent flag, i_understand_key_goes_to_chat=true, leaving no ambiguity about prerequisites.

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