Skip to main content
Glama
aryazansev

Yandex Delivery MCP

by aryazansev

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_PORTNoPort for the MCP HTTP server3002
YANDEX_DELIVERY_API_KEYYesAPI key for Yandex Delivery

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
calculate_offersD–
create_claimD–
get_claim_infoD–
accept_claimD–
cancel_claimD–
check_priceD–
get_tariffsD–
get_driver_phoneD–
get_performer_positionD–
get_points_etaD–
get_tracking_linksD–
get_confirmation_codeD–
get_proof_of_deliveryD–
edit_claimD–
apply_changes_requestD–
apply_changes_resultD–
return_claimD–
search_claimsD–
get_bulk_infoD–
get_claim_journalD–
get_delivery_methodsD–

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

D1.8/5.0

Scored across 21 tools

Disambiguation3/5

The tool set has several overlapping retrieval functions (e.g., get_claim_info, search_claims, get_bulk_info, get_claim_journal) and similar pricing tools (calculate_offers, check_price), which could confuse an agent without detailed descriptions. However, most tools are distinct actions on distinct resources.

Naming Consistency4/5

All tool names use snake_case and follow a verb_noun pattern (get_tracking_links, create_claim, accept_claim, etc.), which is consistent and readable. The only minor inconsistency is mixing singular and plural nouns (claim vs. claims, info vs. journal).

Tool Count4/5

With 21 tools, the server is slightly over the typical comfortable range but still reasonable for a comprehensive delivery management API covering claims, tracking, pricing, and delivery methods. Each tool appears to serve a distinct purpose, so the count is justified.

Completeness4/5

The tool surface covers the full claim lifecycle (create, edit, accept, cancel, return, search) and includes tracking, pricing, and delivery method operations, leaving few obvious gaps. Minor missing features like a dedicated 'delete' action are likely covered by cancel/return, so agents can achieve core workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues