Skip to main content
Glama
Sign In
cdek

cdek

by dontsovcmc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cdek_download_photos

Download a ZIP archive of photos for a document request using its UUID.

Instructions

Скачивание готового архива с фото (GET /v2/photoDocument/{uuid}).

Скачивает архив с фото документов в zip-формате.

Args: uuid: Photo document request UUID output_path: Absolute path to save the zip archive

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>",
      "output_path": "<output_path>"
    },
    "name": "cdek_download_photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes
output_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It only states it downloads a zip archive via GET, but does not disclose what happens if the file already exists, network error handling, size limits, or that it is a read-only operation.

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 brief and front-loaded with the main action. It includes an args list but could be slightly more concise by integrating the parameter explanations into the prose; however, it is not overly verbose.

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?

While an output schema exists, the description lacks important context: it does not mention the dependency on cdek_request_photos, file overwrite behavior, or error handling. For a tool with no annotations, these gaps reduce completeness.

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 description explains both parameters: uuid is 'Photo document request UUID' and output_path is 'Absolute path to save the zip archive'. Since schema coverage is 0%, this adds necessary meaning beyond the schema.

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 tool downloads a ready archive of photos in zip format, and mentions the specific HTTP method and endpoint. Among siblings, it distinguishes itself from cdek_request_photos which likely is used to request the photos initially.

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 is provided on when to use this tool versus alternatives, such as cdek_request_photos, or what prerequisites are needed (e.g., a valid UUID from a prior request).

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