Skip to main content
Glama
ztemerbekov

A1 Yandex KIT MCP

by ztemerbekov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get order delivery labels

get_order_delivery_labels
Read-only

Fetch delivery labels for order chunks, receiving PDFs with address, tracking number, and barcode. Handles skipped chunks with reasons and returns available labels.

Instructions

Get the delivery labels (ярлыки) of an order's delivery chunks — the PDF with the address, tracking number and barcode that goes onto the parcel. The first request per chunk and format asks the delivery service for the document, later ones return the same one. The PDF links are signed and expire at expires_at — do not store them, re-request instead. Chunks with no label (self-pickup, delivery not created yet, service that does not print labels, requested format unsupported, or a failure on the service's side — reason GENERATION_FAILED, which is temporary and worth retrying) come back in skipped with a reason, while the remaining chunks still return their labels. For the handover act covering a whole warehouse + service group use generate_order_waybills instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesOrder ID (UUID).
label_formatNoLabel size in millimetres. Omit to let each delivery service use its own default. Which sizes a service prints comes from get_delivery_label_formats: a service in EXPLICIT_FORMATS mode skips the chunk with FORMAT_NOT_SUPPORTED when the size is not on its list, one in PROVIDER_DEFAULT mode ignores this parameter entirely (its labels come back with an empty label_format).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

A5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses meaningful behavior: request caching semantics, signed URL expiration at expires_at, skipped chunks with reasons, and the temporary GENERATION_FAILED case worth retrying. This is far more than the annotation alone provides.

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 dense but each sentence earns its place: what a label is, caching behavior, URL expiry, skipped-chunk semantics, and the sibling alternative. It is front-loaded with the core purpose and stays focused despite covering several edge cases.

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

Completeness5/5

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

For a two-parameter tool with no output schema, this description is complete: it explains return behavior (labels plus skipped reasons), expiry, retry guidance, format-dependent behavior, and the alternative tool. An agent has enough context to call it correctly without further inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds significant meaning beyond the schema, especially for label_format: omitting it uses the provider default, EXPLICIT_FORMATS mode can skip with FORMAT_NOT_SUPPORTED, and PROVIDER_DEFAULT mode ignores the parameter. This helps the agent choose and interpret parameter values correctly.

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 names a specific verb and resource: getting the delivery labels of an order's delivery chunks, and clarifies what the label is (PDF with address, tracking number, barcode). It also explicitly distinguishes this tool from generate_order_waybills, so an agent can tell them apart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear usage context: first request per chunk/format fetches from the delivery service, later ones reuse the same document, and expired links should be re-requested rather than stored. It also names the alternative tool, generate_order_waybills, for the handover-act case.

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