delovye-linii-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DELLIN_API_KEY | Yes | API-ключ из кабинета разработчика: https://dev.dellin.ru/ |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculateB | Расчёт стоимости и сроков доставки Деловыми Линиями. |
| get_citiesC | Поиск городов в справочнике Деловых Линий. |
| trackC | Отслеживание заказа Деловых Линий по номеру накладной. |
| get_terminalsA | Поиск терминалов Деловых Линий в указанном городе. |
| create_orderC | Создание заказа на грузоперевозку в Деловых Линиях. |
| get_order_historyC | Получение истории заказов Деловых Линий. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct operation: calculate pricing, track shipments, search terminals, create orders, view history, and search cities. There is minor overlap potential between calculate (rate/schedule) and create_order (which may imply cost negotiation), and get_order_history vs track could overlap conceptually but generally serve different query types. Overall boundaries are clear enough for an agent.
Most tools follow a clean verb_noun pattern: calculate, get_terminals, create_order, get_order_history, get_cities. Only 'track' deviates as a bare verb rather than verb_noun (e.g. track_order or get_tracking). This is a minor inconsistency but otherwise the naming is predictable and readable.
Six tools is a well-scoped set for a logistics/courier MCP server covering the major user journeys: quoting, booking, tracking, and reference lookups. Each tool clearly earns its place, and the count feels appropriate for the domain.
The surface covers core workflows well: city lookup, terminal lookup, pricing, order creation, order tracking, and order history. Obvious gaps include the ability to cancel or update an order, and there is no document/label generation for shipping, though these are secondary for a courier integration. Core lifecycle is otherwise present.