Skip to main content
Glama
elevanaltd

debate-hall-mcp

by elevanaltd

init_debate

Create a structured debate room with configurable turns, rounds, and cognition validation for multi-perspective decision-making.

Instructions

Create room. mode:fixed|mediated. strict_cognition->validate turns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNofixed
topicYes
max_turnsNo
thread_idYes
max_roundsNo
octave_modeNo
strict_cognitionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It adds a cryptic behavior hint ('strict_cognition->validate turns') but does not explain side effects, whether creation is idempotent, permission needs, or what 'validate turns' actually entails.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short and has no filler, but the telegraphic fragments sacrifice clarity. 'mode:fixed|mediated' and 'strict_cognition->validate turns' are compressed to the point of being cryptic rather than helpful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter tool with no annotations and no schema descriptions, this description is far from complete. It omits required parameters, optional controls, and the tool's place in the debate workflow. The output schema exists but does not compensate for missing invocation guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and there are 7 parameters. The description adds limited semantics for mode ('fixed|mediated') and strict_cognition ('validate turns'), but does not mention thread_id, topic, max_turns, max_rounds, or octave_mode, leaving most parameters unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Create room,' which gives a verb and object, but 'room' is vague and doesn't explicitly say 'debate room' or distinguish this from sibling tools like convene or run_debate. The tool name init_debate provides some disambiguation, but the description itself lacks specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use init_debate versus alternatives such as add_turn, run_debate, or convene. It does not state prerequisites, ordering, or scenarios where another tool would be more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.