Skip to main content
Glama
Sign In
cdek

cdek

by dontsovcmc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cdek_client_return

Register a client-initiated return for delivered orders in internet shops. Creates return delivery using specified tariff code.

Instructions

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

Оформление возврата для интернет-магазинов. Создается только для заказов в конечном статусе "Вручен". Отличие от обычного возврата: возврат оформляет сам клиент.

Args: uuid: Order UUID (идентификатор прямого заказа) tariff_code: Tariff code for return delivery (e.g. 136)

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>",
      "tariff_code": "<tariff_code>"
    },
    "name": "cdek_client_return"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes
tariff_codeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses that it creates a client-return only for delivered orders, but lacks details on side effects (e.g., order status changes), authentication, or success/error outcomes.

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?

Concise, front-loaded with purpose and endpoint, then conditions and args. 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?

Covers purpose, conditions, and parameters. Output schema exists (context signal), so return info is not needed. But missing behavioral details like error cases or permissions, which could improve completeness.

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 has 0% description coverage; description adds meaning for both parameters: uuid is Order UUID, tariff_code is Tariff code for return delivery with an example. This compensates for schema gaps.

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?

Description clearly states it registers a client return, specifies endpoint, and distinguishes from ordinary returns. It is specific to client returns for internet shops and only for delivered orders, differentiating it from siblings like cdek_order_refusal.

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?

Specifies when to use: for internet shops, only for orders in 'Delivered' status. Contrasts with ordinary return, but does not explicitly mention when not to use or name alternative tools.

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