Council Blackboard
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| system_statusB | Return deployment identity, state model, and current chamber counts. |
| blackboard_get_stateA | Retrieve the shared Council Blackboard state. |
| blackboard_add_itemC | Commit a new item directly to the shared blackboard. |
| blackboard_propose_inputD | Submit a candidate mutation through the Human-In-The-Loop boundary. |
| blackboard_approve_proposalB | Approve or reject a pending proposal at the HITL supervisory boundary. |
| blackboard_set_modeC | Switch the operating mode of the Council Blackboard. |
| colloquium_get_sessionC | Inspect the current AI-first colloquium session. |
| colloquium_interjectB | Insert a high-priority supervisor directive into the colloquium stream. |
| colloquium_commit_to_blackboardD | Commit a distilled colloquium outcome into the shared blackboard. |
| colloquium_update_rule_of_motionB | Update colloquium turn structure, consensus threshold, or active topic. |
| audit_get_recentB | Return recent mutating MCP calls from the in-process audit log. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| deliberate_problem | Create a council-deliberation instruction using current shared-state boundaries. |
| evaluate_blackboard_proposal | Create a supervisory review prompt for a pending blackboard proposal. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| blackboard_state_resource | Current complete blackboard state. |
| colloquium_session_resource | Current complete colloquium session. |
| agent_manifest_resource | Current agent manifest. |
TDQS
Scored across 11 tools
Some overlap exists: blackboard_add_item and colloquium_commit_to_blackboard both write to the blackboard, and get_state/get_session could be confused. However, descriptions clarify direct vs. distilled and state vs. session, so most tools have distinct purposes.
Most tools follow a <domain>_<action> pattern (e.g., blackboard_get_state, colloquium_interject), but 'system_status' lacks a verb, breaking the otherwise consistent naming scheme.
With 11 tools, the server is well-scoped, covering blackboard, colloquium, and audit operations without feeling bloated or sparse. This is within the ideal range for a specialized server.
The tool surface covers the core lifecycle of the domain: reading state, adding/proposing/approving items, managing sessions, and auditing. Minor gaps like explicit item deletion or update are not critical, so it feels reasonably complete.