leki-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEKI_STATS | No | Set to 1 to enable anonymous counters under /stats | |
| LEKI_CONTACT | No | Contact information | |
| LEKI_DATA_DIR | No | Directory where the data (~20 MB) is downloaded and cached (defaults to ~/.cache/leki-mcp) | |
| LEKI_PUBLIC_URL | No | Public URL of the server | |
| LEKI_RATE_LIMIT | No | Rate limit for the server | |
| LEKI_REFRESH_HOURS | No | How often the data is refreshed, in hours | 24 |
| LEKI_REFUND_XLSX_URL | No | Direct link to the refund list attachment (.xlsx) |
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 |
|---|---|
| drug_priceA | Official pharmacy price, NFZ refund limit, refund level and patient co-payment of a medicine on the Polish refund list, with cheaper equivalents (same substance, strength and pack size) and the cheapest price per tablet. Also tells if the pack is free for seniors 65+, children under 18 or pregnant women. query: brand + strength ("Tulip 20 mg"), substance ("atorwastatyna 20 mg" / "atorvastatinum"), pack size ("30 szt") or EAN/GTIN. |
| drug_infoC | Data from the Polish Medicinal Products Register: substance, strength, form, ATC, marketing authorisation holder, prescription status (OTC / Rp / Rpz / Rpw / Lz), registered packs with EAN and links to the patient leaflet and SmPC. |
| data_sourcesC | Where the data comes from, how current it is, caveats. |
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 3 tools
The three tools have clearly distinct purposes: drug_price handles reimbursement, co-payment, and price comparisons; drug_info retrieves official registry metadata and leaflet links; data_sources explains provenance. There is no meaningful overlap that would cause an agent to misselect between them.
All tool names use consistent snake_case with descriptive noun phrases (drug_price, drug_info, data_sources). The drug_ prefix groups the two drug lookup tools logically, and data_sources is still stylistically consistent.
Three tools are well-scoped for a focused Polish drug pricing and registry lookup server. Each tool has a clear, non-redundant role, and no obvious operation is missing that would justify adding more tools.
The surface covers the core domain well: pricing/refund data, cheaper equivalents, senior/child/pregnancy exemptions, registry details, pack EANs, leaflets, and data provenance. Minor potential gaps exist around broader discovery or safety/interaction information, but the stated scope is substantially covered.