ai-delivery
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_work_itemsB | List work item IDs, titles, and current revisions. |
| get_contextB | Read the current spec, revision, evidence, and role handoffs. |
| create_work_itemC | Create a versioned work item. |
| update_work_itemC | Create a new work revision, optionally bound to the produced source SHA-256. |
| handoff_workC | Record a role-to-role handoff tied to the current revision. |
| record_evidenceC | Append evidence tied to the current revision, hash, and environment. |
| evaluate_qa_gateC | Evaluate whether current revision has all passing QA evidence. |
| record_release_decisionB | Record caller-supplied release-owner attestation; approval requires the QA evidence gate. |
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 8 tools
Each tool targets a distinct lifecycle action (list, get, create, update, handoff, record evidence, evaluate gate, record decision), and descriptions clarify the boundaries. However, 'get_context' is somewhat broad and could be confused with 'list_work_items' or overlaps with update/handoff in terms of reading revision state.
All tools follow the consistent verb_noun pattern (e.g., list_work_items, update_work_item, record_evidence), with predictable snake_case and clear action-oriented prefixes.
Eight tools are well-scoped for the domain of managing versioned work items, evidence, handoffs, and gated releases, with each tool earning its place without obvious redundancy.
The surface covers the core lifecycle from creation to release decision, including evidence and QA gates. However, it lacks explicit deletion or archival operations, and evidence retrieval is only implicit through get_context, which may limit some workflows.