Yevgeny
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OLLAMA_URL | No | URL of the Ollama server | http://127.0.0.1:11434 |
| YEVGENY_NODE | No | Path to Node executable for the Windows yevgeny.cmd helper; only used when node is not on PATH | |
| YEVGENY_MODEL | No | Ollama model name; must support tool calling | gemma4:12b |
| YEVGENY_PYTHON | No | Path to the Python 3.11+ interpreter; auto-discovered if unset | |
| YEVGENY_ALLOW_PRIVATE_NET | No | Set to '1' to let fetch_url reach LAN/loopback addresses |
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 |
|---|---|
| askA | Ask Yevgeny (the local model) a single self-contained question and get the answer back immediately. No tools, no web access, one turn. Use for summarising, extracting or reformatting text you already have, classifying items, or drafting. For anything needing research, files or computation use delegate_start instead. |
| delegate_startA | Hand a multi-step task to Yevgeny and get a job id back immediately. Yevgeny can search and read files, fetch web pages, write structured output, and run Python (including multi-hour background simulations). Returns at once - poll with delegate_status and collect with delegate_result. Give a thorough brief: state the goal, the sources or directories to use, and the exact output format you want. |
| delegate_statusA | Check how a delegated job is going without blocking: its state, how many steps it has taken, which tools it has called, any background processes it launched and whether they are still alive, and the tail of its log. |
| delegate_resultA | Collect the final report from a delegated job, plus a listing of every file it wrote to its scratch directory. Note that a finished job may still have background processes running - check delegate_status for those. |
| delegate_cancelA | Stop a running delegated job. Aborts the agent loop. Background processes it launched keep running unless kill_children is set. |
| yevgeny_healthA | Check that Yevgeny is usable: Ollama reachable, which models are pulled, the Python interpreter it resolved, and recent jobs. |
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 has a clearly distinct purpose: direct one-turn ask, async delegated job lifecycle (start, status, result, cancel), and health check. delegate_status and delegate_result are separated by live progress versus final output, so there is no real ambiguity.
The delegate_* tools follow a consistent and predictable prefix pattern. ask and yevgeny_health deviate slightly from that convention, but they are readable and clearly labeled, so the overall naming remains coherent.
Six tools is a well-scoped set for a local-agent delegation server. Each tool maps to a necessary operation: direct ask, job start, status polling, result collection, cancellation, and health checking, with no redundant entries.
The tool set covers the full delegated-job lifecycle: start, monitor, collect, and cancel, plus a direct quick-ask path and a health check. Background process handling is also addressed through cancel and status. There are no obvious dead ends for the stated purpose.