Skip to main content
Glama
Sign In
cdek

cdek

by dontsovcmc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cdek_barcode

Generate a PDF barcode for a CDEK order using the tracking number and save it to a specified file path.

Instructions

Формирование и скачивание ШК-места (POST /v2/print/barcodes).

Формирует ШК-место в формате PDF для заказа и сохраняет файл.

Args: cdek_number: CDEK tracking number output_path: Absolute path to save PDF (e.g. /tmp/1234567890.pdf)

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": {
      "cdek_number": "<cdek_number>",
      "output_path": "<output_path>"
    },
    "name": "cdek_barcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
cdek_numberYes
output_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It mentions the tool saves a file to a specified path and uses POST, but does not discuss side effects, permissions, error handling, or file overwrite behavior. Adequate but not thorough.

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?

The description is brief, structured with a title line, a single-sentence explanation, and clear Args list. Every sentence adds value, with no redundancy.

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?

Given the tool's simplicity (2 required params, output schema exists), the description covers purpose, parameters, and output format (PDF). It lacks details on errors or idempotency, but is largely complete for a straightforward file-generation tool.

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?

Schema coverage is 0%, so the description compensates well. It explains cdek_number as 'CDEK tracking number' and output_path as 'Absolute path to save PDF', adding critical meaning beyond the schema's type-only definitions.

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 generates and downloads a barcode in PDF format for an order, using the verb 'формирует и скачивает'. It distinguishes from siblings like cdek_label or cdek_waybill by specifying 'ШК-место' (barcode place), making the purpose unambiguous.

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 provides no explicit guidance on when to use this tool versus its siblings (e.g., cdek_label, cdek_waybill). It implies usage for printing barcodes but does not contrast or exclude other tools.

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