Skip to main content
Glama
Sign In
cdek

cdek

by dontsovcmc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cdek_create_prealert

Inform CDEK about your intention to transfer orders to a warehouse by creating a prealert with planned date, shipment point, and order numbers.

Instructions

Регистрация преалерта (POST /v2/prealert).

Информирование СДЭК о намерении передать заказы на склад. Реестр заказов, которые клиент собирается передать.

Args: planned_date: Planned date YYYY-MM-DD (планируемая дата передачи) shipment_point: Shipment point code (код ПВЗ для передачи, e.g. "MSK005") cdek_numbers: Comma-separated CDEK numbers

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": {
      "planned_date": "<planned_date>",
      "shipment_point": "<shipment_point>",
      "cdek_numbers": "<cdek_numbers>"
    },
    "name": "cdek_create_prealert"
  }
}

Input Schema

NameRequiredDescriptionDefault
cdek_numbersYes
planned_dateYes
shipment_pointYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. However, it only mentions it is a POST request and registers a prealert, without detailing side effects, idempotency, authorization needs, or whether it is destructive. This is insufficient for safe invocation.

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?

The description is short and front-loaded with purpose, using two clear sentences plus parameter lines. It is efficient but could be more structured (e.g., sections). No wasted words.

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

Completeness2/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 does not mention what the response looks like. It also lacks information on prerequisites (e.g., orders must exist), error handling, or next steps. For a tool in a complex logistics system, this is incomplete.

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?

Input schema has 0% description coverage, so the description adds critical meaning: specifies format for planned_date (YYYY-MM-DD), gives an example for shipment_point ('MSK005'), and clarifies that cdek_numbers are comma-separated. This goes beyond the schema names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 prealert and informs CDEK about intention to transfer orders, using the verb 'регистрация' and 'информирование'. It is specific to creating a prealert, distinguishing it implicitly from siblings like cdek_get_prealert.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It only states the action, leaving the agent to infer context from sibling names. No 'when not to use' or alternative tools mentioned.

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