Skip to main content
Glama
CoReason-AI

coreason_multi_agent_debate

Official
by CoReason-AI

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
multiagentdebateA

Structured multi‑persona debate tool.

Call sequence (typical):

  1. Each persona registers once with action:"register".

  2. Personas alternate action:"argue" (fresh point) or "rebut" (counter a targetAgentId).

  3. A special persona (or either side) issues action:"judge" with a verdict text (first line should be "pro", "con", or "inconclusive").

  4. Set needsMoreRounds:false only when the debate is finished and a verdict stands.

Parameters:

  • agentId (string) : "pro", "con", "judge", or any custom ID

  • round (int ≥1) : Debate round number

  • action (string) : "register" | "argue" | "rebut" | "judge"

  • content (string, optional) : Argument text or verdict

  • targetAgentId (string opt.) : Agent being rebutted (only for action:"rebut")

  • needsMoreRounds (boolean) : True if additional debate rounds desired

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.8/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly defined.

Naming Consistency5/5

The single tool name 'multiagentdebate' is descriptive and uses consistent camelCase. There are no naming conflicts to evaluate.

Tool Count3/5

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.

Completeness5/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues