deepwork
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 |
|---|---|
| task_beginA | Record the objective, acceptance criteria, and canonical workspace before repository work begins. |
| inspect_repositoryB | Create a deterministic, concise inventory using ripgrep, Git, manifests, and a symlink/junction scan. |
| record_planC | Persist a concrete plan after inspection and before any write is allowed. |
| run_verificationA | Execute one planned test/lint/check/build command from the untrusted repository without a shell, fingerprinting the workspace before and after. Repository-controlled code can spawn processes, access the network, or destructively mutate files; a detected mutation makes verification fail. Alternatively, record specific evidence that no executable tests apply. |
| task_statusB | Return the append-only evidence state and current quality-gate stage for a task. |
| final_gateA | Refuse PASS unless inspection, plan, post-change verification, diff summary, and every acceptance-evidence item exist. |
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 distinct purpose: starting a task, inspecting, planning, verifying, checking status, and final gating. No overlap in functionality.
All tool names follow a consistent verb_noun snake_case pattern (e.g., inspect_repository, record_plan).
6 tools is appropriate for a focused workflow covering task initiation, inspection, planning, verification, and status reporting.
The set covers the main workflow stages but lacks a tool for applying changes or modifying the repository, which may be outside scope.