ai-discuss
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZHIPU_API_KEY | No | API key for Zhipu (GLM) participant if configured. | |
| DEEPSEEK_API_KEY | No | API key for DeepSeek participant if configured. | |
| AI_DISCUSS_CONFIG | No | Path to the configuration file for participants and server options. | ai-discuss.config.json |
| DASHSCOPE_API_KEY | No | API key for DashScope (Qwen) participant if configured. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discussA | Fan out a topic + code context to configured AI participants, run an N-round debate where they critique and refine each other's answers, then return a synthesized, ranked recommendation. Writes a full markdown transcript to disk. |
| list_participantsA | List the AI participants configured for the ai-discuss server, including type, model, whether they are enabled/available, and which is the default synthesizer. Useful before calling discuss. |
| list_modelsA | Query each configured provider (OpenRouter, Ollama, ...) for the model ids it can serve. Useful to discover valid model names before editing the config or choosing participants. |
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 3 tools
Each tool serves a distinct purpose: discuss runs the debate, list_models discovers available models, and list_participants shows configured participants. No functional overlap.
All tools use consistent snake_case verb_noun naming (discuss, list_models, list_participants), with a clear pattern.
Three tools is well-scoped for this focused server; each tool plays an essential role without redundancy.
Tools cover the main discussion task and listing of resources, but lack create/update/delete operations for participants or models, leaving configuration management to external means.