zahadun
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zahadun_peersC | Kto jest w siatce zahadun i co umie (z AgentCards). |
| zahadun_askA | Zleca zadanie peerowi w siatce. Zwraca identyfikator zadania - wynik odbierz przez zahadun_task. |
| zahadun_taskA | Odbior wyniku lub statusu zadania. |
| zahadun_modelsA | Zywy katalog modeli toru opencode wraz z cenami (z lokalnego serwera OpenCode). Model spoza katalogu jest bledem, nigdy cichym podstawieniem. |
| zahadun_memory_searchA | Przeszukuje pamiec mesh po tresci (ripgrep po katalogu toru). |
| zahadun_memory_readC | Odczyt tematu (po contextId) albo wpisu wspolnego (po slugu). |
| zahadun_memory_writeA | Zapis do pamieci mesh. |
| zahadun_memory_topicsC | Lista tematow i wpisow wspolnych w pamieci mesh. |
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 8 tools
Each tool targets a distinct function: peer discovery, task submission, task status retrieval, model catalog, memory search, read, write, and topic listing. There is no overlap between task and memory operations, and request/response pair (ask/task) is clearly separated.
All tools share the 'zahadun_' prefix, and the memory tools follow a 'memory_<action>' pattern. However, some names are bare nouns (peers, task, models) while others are verbs (ask) or compound nouns (memory_topics), creating minor inconsistency in naming style.
With 8 tools, the set is well-scoped for the server's purpose of managing an agent mesh network, task delegation, and shared memory. Each tool serves a clear role without redundancy or bloat.
Core workflows are covered: task lifecycle (submit, retrieve status/result), peer discovery, and memory operations (write, read, search, list). Minor gaps exist such as no task cancellation or listing of all tasks, but these are not essential for the primary use case.