Skip to main content
Glama
Sign In
cdek

cdek

by dontsovcmc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cdek_create_webhook

Create webhook subscriptions to receive CDEK delivery events like order status changes, print form generation, or delivery updates at a specified URL.

Instructions

Добавление подписки на вебхуки (POST /v2/webhooks).

Типы: ORDER_STATUS, PRINT_FORM, PREALERT_CLOSED, ACCOMPANYING_WAYBILL, ORDER_CHANGED, DELIVERY_COST_CHANGED, DELIVERY_PROBLEM, DELIVERY_DATE_CHANGED, ORDER_MODE_CHANGED, COURIER_INFO.

Args: type: Webhook type (e.g. ORDER_STATUS, PRINT_FORM) url: URL to receive webhook events

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": {
      "type": "<type>",
      "url": "<url>"
    },
    "name": "cdek_create_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
typeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action and HTTP method, but does not disclose side effects, authentication needs, idempotency, or any other behavioral traits.

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 concise and front-loaded with the main action, followed by a list of types and parameter explanations. It is efficient with no wasted words.

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?

Given two simple parameters and an output schema, the description covers the basic functionality. However, it lacks behavioral context and usage guidance, leaving gaps in completeness.

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?

With 0% schema description coverage, the description adds value by listing the parameters and giving examples for 'type' (e.g., ORDER_STATUS), though it lacks format constraints or further details for 'url'.

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 it is for adding a webhook subscription, specifies the HTTP method and path, and lists the available webhook types, distinguishing it from sibling tools like list, get, delete.

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

Usage Guidelines3/5

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

The description implies the tool is for creating webhooks, but does not provide explicit guidance on when to use it versus alternatives like cdek_list_webhooks or cdek_delete_webhook.

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