deus-witness
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEUS_DEMO_OUT | No | Where the demo upstream records its effects | |
| DEUS_WITNESS_KEY | Yes | Agent key (dwk_...) from https://witness.sipkigroup.com | |
| DEUS_WITNESS_HOME | No | State directory |
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 |
|---|---|
| send_emailB | Send an email (demo: only recorded). |
| purchaseC | Buy something (demo: only recorded). |
| delete_resourceB | Delete a resource (demo: only recorded). |
| publishB | Publish text to a channel (demo: only recorded). |
| read_fileA | Read a file (demo: returns fixed text, reads nothing). |
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 5 tools
Each tool targets a clearly distinct action and resource type: email, purchase, deletion, publishing, and file reading. There is little risk of an agent confusing one tool with another.
Most names use verb_noun form (send_email, delete_resource, read_file), but purchase and publish are standalone verbs. The conventions are mixed but still readable and predictable enough.
Five tools is a reasonable, compact set. Each tool represents a distinct operation, so the count is well-scoped rather than bloated.
The surface is disjointed: delete_resource exists with no create/update/read resource tools, read_file has no write counterpart, and purchase/send_email/publish have no lifecycle operations. This leaves significant gaps for most plausible domains.