cdek

by dontsovcmc

Overview Schema Source Related Servers Discussions Admin

Python

Local

cdek_create_delivery

Instructions

Регистрация договоренности о доставке (POST /v2/delivery).

Фиксирует оговоренные с клиентом дату и время доставки (приезда курьера), а также позволяет изменить адрес доставки.

At least one of cdek_number or order_uuid must be provided.

Args: date: Delivery date YYYY-MM-DD (согласованная с получателем) cdek_number: CDEK order number order_uuid: Order UUID (alternative to cdek_number) time_from: Delivery time from HH:MM (обязательно для "до двери") time_to: Delivery time to HH:MM (обязательно для "до двери") comment: Comment for delivery delivery_point: Delivery point code (обязательно для "до склада")

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": {
      "date": "<date>"
    },
    "name": "cdek_create_delivery"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes
`comment`	No
`time_to`	No
`time_from`	No
`order_uuid`	No
`cdek_number`	No
`delivery_point`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Jul 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description bears full burden. It explains the action (registering an agreement) and conditions for time/address fields but omits side effects, permissions, or error cases.

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

Conciseness3/5

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

The description mixes Russian and English, and includes an API path and parameter list. It is somewhat verbose; could be more concise by removing redundant 'Args' lines after already listing them.

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

Completeness3/5

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

Output schema exists, so return values need not be described. However, the description lacks usage scope (when to use) and does not cover non-parameter behaviors like side effects or prerequisites.

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 coverage is 0%, but the description lists all 7 parameters with explanations and additional constraints (e.g., time_from/time_to mandatory for 'до двери', delivery_point for 'до склада', and the requirement for at least one of cdek_number/order_uuid).

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 delivery agreement via POST /v2/delivery, fixing date/time and allowing address changes. It distinguishes from siblings like cdek_create_order and cdek_get_delivery.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives (e.g., cdek_get_delivery, cdek_create_order). Only parameter constraints (at least one of cdek_number or order_uuid) are given.

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

Deploy Server