chestny-znak-mcp-ru

by ilyautov

Overview Schema Source Related Servers Discussions Admin

Python

Remote

crpt_set_key

Idempotent

Rotate an expired or leaked Chestny ZNAK API key from chat after confirming the key will appear in the transcript.

Instructions

Change / rotate the API key from chat (e.g. the old one expired or leaked).

⚠️ The key goes into the chat transcript — requires i_understand_key_goes_to_chat=true. The safe, terminal-free alternative is the installer, where the key never enters chat. Use a scoped key and rotate it in the seller cabinet if it was exposed.

Args: credentials: dict with the required fields ({fields}). cabinet: which cabinet to update. Default: the active one (so "my key expired" just works). If there is none, the cabinet is named from the marketplace's shop name, else "main". i_understand_key_goes_to_chat: must be true to proceed. On success the key is validated against the marketplace and the shop name is reported. Saved locally (chmod 600), never echoed back.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cabinet`	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.2.0Sep 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Goes well beyond annotations: discloses that the key enters the chat transcript, requires a hard acknowledgment, validates against the marketplace, and is stored chmod 600 and never echoed. Annotations say only idempotent/non-destructive. Some borderline tension between key-entry-into-chat and 'destructiveHint: false', but the description clarifies it is non-destructive rotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded action and a clear warning, with Args and return behavior in a predictable structure. Slightly loose with the {fields} placeholder and parenthetical examples, but no real waste for a security-sensitive tool.

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?

Covers urgency, safety alternative, parameter behavior, validation, storage permissions, response handling, and rotation advice. With an output schema present, it correctly does not belabor return values, so nothing an agent needs to call it safely is missing.

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?

Schema coverage is 0% and default-empty cabinet/boolean, so the description does the heavy lifting: it explains cabinet defaulting logic (active cabinet, else shop name, else 'main'), what credentials must contain (via the {fields} placeholder), and the exact semantics of the acknowledgment flag. Only the credential field list is a runtime placeholder, capping it below 5.

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?

States a specific verb+resource ('Change / rotate the API key'), gives concrete triggers (expired or leaked), and the chat-context framing makes it unmistakable against the auth/cabinet siblings like crpt_check_auth and crpt_use_cabinet.

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

Usage Guidelines4/5

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

Explicit about when to use it here vs the installer alternative (safe, terminal-free), and warns about scoped keys and rotation in the seller cabinet. No explicit exclusions vs the other 13 siblings, but the alternative routing is clear.

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

Install Server