Skip to main content
Glama
Sign In
cdek

cdek

by dontsovcmc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cdek_order_refusal

Register a refusal for an order in any status before it is delivered or marked as not delivered, triggering a return to the online store.

Instructions

Регистрация отказа (POST /v2/orders/{uuid}/refusal).

Регистрация отказа от заказа и возврат в интернет-магазин. Заказ может быть отменен в любом статусе до "Вручен"/"Не вручен". Для статуса "Создан" рекомендуется использовать удаление заказа.

Args: uuid: Order UUID to refuse

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": {
      "uuid": "<uuid>"
    },
    "name": "cdek_order_refusal"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.1/5.0
Behavior3/5

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

The description discloses the HTTP method (POST) and endpoint, and the action of registering refusal. However, it does not mention side effects like status changes, notifications, or permissions. With no annotations, it is adequate but not comprehensive.

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?

Concise with two meaningful sentences plus an args line. Structure is clear: purpose, conditions, parameter. No unnecessary words.

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

Completeness4/5

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

Given the tool's simplicity (one required parameter) and existence of output schema, the description covers the essential: action, conditions for use, and alternative. It could add more on response but is sufficiently complete.

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

Parameters3/5

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

The description specifies that the 'uuid' parameter is the order UUID to refuse, adding meaning beyond the schema's type-only definition. With 0% schema description coverage, this compensates partially but lacks format or source details.

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 tool registers a refusal (cancellation) of an order and triggers return to the online store. It specifies the HTTP endpoint and distinguishes itself from deletion for 'Created' status orders.

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?

Explicitly states cancellation is allowed in any status before 'Delivered'/'Not delivered' and recommends using delete order for 'Created' status, providing clear when-to-use and when-not-to-use guidance with an alternative.

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

Deploy Server

Other Tools