lk-tko-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LK_BASE_URL | No | Base URL of the lk-tko-v2 REST API instance. Defaults to the local dev instance. | http://localhost:8080 |
| LK_PASSWORD | Yes | Password for OAuth2 password grant authentication to lk-tko-v2. | |
| LK_USERNAME | Yes | Login (username) for OAuth2 password grant authentication to lk-tko-v2. | |
| LK_CLIENT_ID | Yes | OAuth2 client ID for accessing the lk-tko-v2 CUBA REST API. | |
| LK_CLIENT_SECRET | Yes | OAuth2 client secret for accessing the lk-tko-v2 CUBA REST API. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Проверка того, что сервер жив и подключён. |
| get_contragent_statusB | Найти контрагента ЛК по ИНН и вернуть его данные. Возвращает найденную сущность Contragent целиком через REST API lk-tko-v2 — отдельного поля "статус" может не быть, это нужно смотреть по реальным данным, которые вернёт CUBA REST. |
| get_contragent_debtA | Долг контрагента (основной долг, пени, госпошлина) по лицевому счёту или ИНН. |
| get_debt_by_phoneB | Долг по всем лицевым счетам, привязанным к телефону. |
| get_debt_by_emailB | Долг по всем лицевым счетам, привязанным к email. |
| get_serviced_periodsB | Периоды обслуживания (даты начала/окончания) лицевого счёта или ИНН. |
| get_calculation_amount_typeC | Тип расчёта начислений и текущий долг по лицевому счёту/ИНН. |
| get_contragent_billsB | Счета контрагента за период. contragent_id — UUID контрагента (см. поле "id" в get_contragent_status). date_from/date_to — даты в формате dd.MM.yyyy. |
| get_contractB | Список договоров контрагента с суммами начислений/платежей/пеней/долга. contragent_id — UUID контрагента (см. поле "id" в get_contragent_status). |
| get_fine_detailsA | Детализация пеней по лицевому счёту за период, по договорам и месяцам. date_from/date_to — даты в формате dd.MM.yyyy. |
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 10 tools
There are several debt-related tools (get_contragent_debt, get_debt_by_phone, get_debt_by_email, get_calculation_amount_type, get_contract) whose outputs overlap in debt/penalty figures; descriptions clarify different lookup keys or levels, but an agent could still struggle to choose among them. ping and the document/period tools are clearly distinct.
All tools follow a get_ prefix and snake_case, and most use a readable get_<resource>_<detail> or get_<detail>_by_<identifier> pattern. The deviations are minor: ping has no get_, and names like get_calculation_amount_type are less intuitive than the rest.
Ten tools is a reasonable size for a debt/contract lookup server. Each tool covers a distinct query need without excessive redundancy or an overwhelming surface.
The set provides solid read-only coverage: contragent lookup, debt by multiple identifiers, bills, contracts, service periods, and fine details. A minor gap is the lack of a direct debt lookup by contragent UUID, which would require using an INN from get_contragent_status as a workaround.