conversation-council
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLUGIN_DATA | No | Optional path for derived data. Overrides the default ~/.codex/conversation-council/ 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| council_statusA | Report local history, index, and runtime readiness. |
| index_workspaceC | Index visible Codex task messages for an allowed workspace. |
| search_historyB | Find relevant evidence-backed councillors in local history. |
| get_evidenceA | Resolve opaque evidence IDs inside the requested workspace. |
| list_pinsA | List historical Codex tasks pinned as preferred councillors. |
| set_pinC | Pin or unpin an indexed historical Codex task. |
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 6 tools
Each tool addresses a distinct operation: status, indexing, searching, evidence resolution, and pin management. No overlapping responsibilities; descriptions clarify the boundaries.
Tool names mostly follow verb_noun pattern (index_workspace, search_history, get_evidence, list_pins, set_pin). council_status breaks the pattern as a noun phrase, and singular/plural consistency varies slightly (list_pins vs set_pin).
With 6 tools, the scope is tightly focused on the conversation history and pinning workflow. Each tool serves a clear purpose without redundancy.
The server covers the full workflow: index, search, resolve evidence, manage pins, and check status. Pin/unpin handled in set_pin, and listing pins covered; no obvious missing operations for the stated purpose.