diaskor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| dss_hesaplaA | Hemodiyaliz hastası için Diyaliz Stabilite Skoru (DSS v2.0.0) hesaplar. 0–28 puan, yüksek puan = iyi. 19–28 stabil, 10–18 yakından izle, <10 acil değerlendir. Kırmızı bayraklar (K ≥ 6.5, albumin < 2.5) toplamdan bağımsız alarm verir. Her parametre için puan, renk, trend ve hekime yönelik bağlam mesajı döner. Eksik parametreler raporlanır. Hasta kimliği (isim, TC) GİRİLMEMELİDİR; araç veri saklamaz. Klinik karar desteğidir, hekim kararının yerini almaz. |
| dss_yontemA | Diyaliz Stabilite Skoru'nun parametrelerini, puan eşiklerini ve karar aralıklarını döner. |
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 2 tools
The two tools have clearly distinct purposes: dss_hesapla performs the score calculation, while dss_yontem returns methodology, parameters, thresholds, and decision ranges. An agent can easily choose between calculating a result and looking up how the score works.
Both tools use the same dss_ prefix and are readable as a related pair. One name is action-oriented (hesapla) while the other is noun-oriented (yontem), so the pattern is slightly mixed but still predictable.
Two tools is on the low end, but appropriate for a narrow single-score clinical calculator: one calculates and one explains the method. No unnecessary tools are included.
The surface covers the core lifecycle of this domain: computing the DSS and exposing the scoring method, thresholds, and interpretation. Calculation-side features such as missing-parameter reporting, red flags, and per-parameter context are included in the calculation result.