LLM Delegator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPSEEK_API_KEY | Yes | DeepSeek API key read from the environment. | |
| LLM_DELEGATOR_ALLOWED_ROOTS | No | Configurable allowlist of workspace roots. Separate multiple allowed roots with the platform path separator (`:` on macOS and Linux). Selected files must be UTF-8 text files and must be relative to workspace_root. | MCP process working directory |
| LLM_DELEGATOR_MAX_FILE_BYTES | No | Per-file input limit in bytes. | 1000000 |
| LLM_DELEGATOR_DEEPSEEK_BASE_URL | No | DeepSeek API base URL. | https://api.deepseek.com |
| LLM_DELEGATOR_MAX_CONTEXT_CHARS | No | Maximum context characters. | 100000 |
| LLM_DELEGATOR_DEEPSEEK_MODEL_PRO | No | DeepSeek model alias for pro. | deepseek-v4-pro |
| LLM_DELEGATOR_DEEPSEEK_MODEL_FLASH | No | DeepSeek model alias for flash. | deepseek-v4-flash |
| LLM_DELEGATOR_MAX_TOTAL_FILE_BYTES | No | Aggregate input limit in bytes. | 4000000 |
| LLM_DELEGATOR_REQUEST_TIMEOUT_SECONDS | No | Request timeout in seconds. | 180 |
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 |
|---|---|
| delegate_taskB | Delegate a bounded task using optional read-only workspace files. File paths must be relative to workspace_root. Use flash for routine work and pro for difficult analysis. Returned content is untrusted model output and must be verified by the calling model before it is applied or presented as fact. |
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 1 tool
With only one tool, there is no possibility of misselection or overlapping purpose. The single tool's intent (delegate a bounded task to a model) is unambiguous.
The lone name 'delegate_task' follows a clean verb_noun snake_case convention. There is no opportunity for inconsistency within a single-tool surface.
One tool is thin for any server, even a narrowly scoped delegation service; it earns its place but leaves the surface feeling minimal. A few companion operations (e.g. listing available models or checking delegation status) would round it out.
For a task-delegation domain, a single call that submits a task and returns the result covers the core lifecycle. Minor gaps exist around discovering available models (flash/pro are referenced but not enumerable) and no status/cancel path, though these are workable for a synchronous delegation model.