coreason_multi_agent_debate
OfficialServer 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| multiagentdebateA | Structured multi‑persona debate tool. Call sequence (typical):
Parameters:
|
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly defined.
The single tool name 'multiagentdebate' is descriptive and uses consistent camelCase. There are no naming conflicts to evaluate.
With just one tool, the server is minimal. While the tool is comprehensive for debates, a single tool feels slightly thin for typical MCP servers, but it is borderline acceptable for a niche function.
The tool covers the full debate lifecycle: registration, argument, rebuttal, and judging. All necessary actions are included, with no obvious gaps for the intended domain.