Skip to main content
Glama
Sign In
cdek

cdek

by dontsovcmc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cdek_delivery_intervals

Retrieve available delivery dates and time intervals for an existing CDEK order using the order number or UUID.

Instructions

Получение интервалов доставки (GET /v2/delivery/intervals).

Возвращает доступные даты и временные интервалы для регистрации договоренности о доставке по уже созданному заказу.

At least one of cdek_number or order_uuid must be provided.

Args: cdek_number: CDEK order number order_uuid: Order UUID

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cdek_delivery_intervals"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_uuidNo
cdek_numberNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.6/5.0
Behavior4/5

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

Since no annotations are provided, the description carries full burden. It explicitly states it is a GET operation that returns dates and intervals, implying no side effects. Could mention that no modifications occur.

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?

Description is reasonably concise and structured: API endpoint, functionality, parameter requirement, and parameter list. Mixing Russian and English is a minor drawback but not excessive.

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?

With an output schema present, the tool description does not need to detail return format. However, it does not explain the business context (e.g., when intervals apply) or any constraints on the intervals.

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?

Schema has 0% description coverage, so description must compensate. The Args section gives one-line descriptions for cdek_number and order_uuid and states that at least one is required. This adds some meaning but is minimal; e.g., no format or source details.

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?

Description clearly states it retrieves delivery intervals for an existing order (GET endpoint). However, it does not differentiate from sibling tools like cdek_estimated_intervals, which might serve a similar purpose.

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?

Specifies the prerequisite that at least one of cdek_number or order_uuid must be provided. Does not provide guidance on when to use this over other tools, nor exclusion criteria.

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