universal-agent-control-plane
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UACP_DATA_DIR | No | Directory where server data, SQLite state, audit events, and logs are stored. | |
| UACP_REGISTRY_ROOT | No | Path to the registry root directory containing the canonical instructions, skills, prompts, and manifest. |
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 |
|---|---|
| registry_validateB | Validate the canonical registry and return actionable errors. |
| registry_resolveB | Resolve a profile into effective instructions and skill metadata. |
| registry_searchB | Search instruction, skill, and prompt documents. |
| skill_runB | Run an allow-listed skill, reloading its implementation after source changes. |
| orchestrateC | Route one skill result to an agent target or a broadcast result envelope. |
| state_getA | Read a namespaced value from shared local state. |
| state_putB | Write a namespaced value to shared local state and audit the mutation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review_code | Create a code-review request using the canonical prompt template. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| registry_manifest | Return the canonical registry manifest. |
| skill_catalog | List portable Agent Skills available in the registry. |
TDQS
Scored across 7 tools
Each tool targets a different concern: orchestration, state read/write, registry lookup/validation/resolution, and skill execution. Even the two registry tools are clearly separated by search versus resolve/validate semantics.
Most tools follow a domain-prefix_verb pattern (state_get, state_put, registry_search, skill_run, registry_validate, registry_resolve), but orchestrate breaks the pattern by using a bare verb with no prefix. The inconsistency is minor and the names remain readable.
Seven tools is a well-scoped size for a control plane server. Each tool covers a distinct function without redundancy, and the count is neither too thin nor too heavy.
The core surface is fairly complete: state read/write, registry search/validate/resolve, skill execution, and result orchestration are all present. Minor gaps exist, such as no explicit state deletion or registry modification, but agents can work around them with the available tools.