boardroom-agents
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROVIDER | No | The LLM provider to use. Default is 'mock' for offline deterministic mode. Set to 'openai' to use OpenAI. | mock |
| OPENAI_API_KEY | No | Your OpenAI API key. Required if PROVIDER is set to 'openai'. |
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_meetingsA | List all board meetings (id, date, title). |
| get_meetingA | Get one meeting's agenda, minutes, attendees, and attached documents. |
| list_motionsA | List motions (id, title, kind, ballot_mode, status). Optionally filter by meeting. |
| get_motion_resultsA | Get results for a motion. Recorded motions return per-voter names and choices. Anonymous motions and elections return ONLY totals and turnout -- never individual votes. |
| search_documentsA | Full-text search over indexed meeting documents. Returns matching snippets with document and meeting references. (Ballot-bearing documents are excluded from this index.) |
| ask_boardA | Ask a natural-language question about the board's history. The answer is drafted by a research agent, then reviewed against the board's answer policy before it is returned. Includes the governance verdict and any policy rules that fired. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Answer policy | The governance policy every answer is evaluated against, in full. |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: listing vs getting details for meetings, listing motions vs getting their results, full-text search, and natural-language query. No overlap.
All tools follow a consistent verb_noun pattern in snake_case, e.g., list_meetings, get_meeting, search_documents. Minor singular/plural variations are acceptable.
With 6 tools, the server is well-scoped for a board information retrieval system. Not too few to be thin, not too many to be overwhelming.
The tool surface covers all major query needs: listing meetings, getting meeting details, listing motions, retrieving motion results, document search, and a Q&A system. It is complete for its apparent read-only purpose.