Skip to main content
Glama
Sign In
cdek

cdek

by dontsovcmc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cdek_get_order

Retrieve detailed order information by UUID, including orders created through other channels.

Instructions

Получение информации о заказе по UUID (GET /v2/orders/{uuid}).

Возвращает детальную информацию о ранее созданном заказе по его идентификатору. Также позволяет получить информацию о заказах, созданных через другие каналы.

Args: uuid: Order 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_get_order"
  }
}

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
Behavior3/5

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

No annotations provided, so description must disclose behavior. It states GET method (safe, read-only) and returns detailed info. No mention of auth requirements, rate limits, or error handling. Adequate but could be more transparent about response format.

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, with a clear structure including an Args section. The information is front-loaded with the main action. Could be slightly shorter, but effective.

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

Completeness4/5

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

Simple retrieval tool with one parameter and output schema provided elsewhere. Description covers the basic purpose and parameter. Lacks mention of error responses or common pitfalls, but sufficient for a straightforward read operation.

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?

Only one parameter (uuid) with 0% schema coverage. Description adds that it is the order UUID in CDEK system, but does not specify format or constraints. Partially compensates for missing schema descriptions.

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 the tool retrieves order information by UUID via GET endpoint. It mentions it works for orders created through other channels. However, it does not explicitly differentiate from sibling cdek_get_order_by_im_number, which serves a similar purpose but by IM number.

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?

Description implies use when UUID is available, but no explicit guidance on when not to use or alternatives like cdek_get_order_by_im_number. No exclusions or prerequisites 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