Skip to main content
Glama
Sign In
cdek

cdek

by dontsovcmc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cdek_delete_webhook

Delete a webhook subscription by providing its UUID to stop receiving notifications.

Instructions

Удаление подписки по UUID (DELETE /v2/webhooks/{uuid}).

Args: uuid: Webhook subscription UUID

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_delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.5/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 carry the burden. It states it's a DELETE operation (destructive) but does not disclose side effects, return value, authorization requirements, or error handling. This is insufficient for a tool that performs a mutation.

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?

Extremely concise with only two lines (one for endpoint, one for parameter). No wasted words; information is front-loaded. For a simple tool with one parameter, this structure is ideal.

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 the tool's simplicity (one param, deletion operation) and the existence of an output schema, the description is minimally adequate. However, it lacks context about when deletion is appropriate, what happens after, or any notes on idempotency. It meets the bare minimum but could be more helpful.

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?

The input schema has 0% coverage (parameter only titled 'Uuid'), but the description adds semantic value: 'uuid: Webhook subscription UUID' clarifies the parameter's purpose and domain. This compensates for the schema deficiency.

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 action ('Удаление подписки' = delete subscription) and the resource (webhook by UUID), with the HTTP method and endpoint. It distinguishes from sibling webhook tools (create, list, get) by specifying deletion.

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 guidance on when to use this tool versus alternatives (e.g., when you need to remove a webhook subscription). No prerequisites or conditions mentioned. The description assumes the user already knows the UUID and the need for deletion.

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