Deed
OfficialServer 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deed_checkA | Check a Deed program and report what the compiler found. Writes one JSON object a line. A |
| deed_testA | Run a Deed program's tests: every |
| deed_runA | Run a Deed program's |
| deed_fmtA | Format a Deed program into the one layout the formatter chooses. Returns the formatted text, or the parse diagnostics when the file does not parse, because a file with no tree has no layout to pick. |
| deed_fixA | Apply every machine-applicable repair the compiler offers and return the repaired program. Only the repairs |
| deed_explainA | Explain one diagnostic code, such as DEED4025. Returns the page that code carries: what it means, why the rule exists, and usually an example. |
| deed_reviewA | Compare the checked module set before a patch with the set after it. Returns one JSON review receipt naming authority additions, obligation tier regressions and newly introduced Guarded obligations. An optional policy object accepts |
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 7 tools
Each tool targets a distinct operation in the Deed toolchain: static checking, test execution, running main, formatting, auto-fixing, diagnostic explanation, and patch review. There is no overlap in their inputs or outputs, so an agent can reliably select the right tool for a given task.
All tools share the `deed_` prefix and a simple verb-based naming scheme (check, test, run, fmt, fix, explain, review). The only minor inconsistency is the abbreviation 'fmt' instead of 'format', but the pattern is otherwise uniform and predictable.
Seven tools is well within the ideal range for a domain-specific language server. Each tool covers a core workflow step (check, test, run, format, fix, explain, review) and none are superfluous or redundant.
The set provides a complete lifecycle for interacting with Deed programs: static checking, testing, execution, formatting, automated repair, diagnostic explanation, and change review. No obvious essential operation is missing; the only conceivable additions (e.g., a build tool) fall outside the apparent scope of this server.