A
licenseA
qualityB
maintenanceDynamic multi-agent debate MCP server for structured argumentation and reasoning among AI agents.
1
7
MIT
la-caja-mcp
by deviceargent
Related Servers
Alternatives to la-caja-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceFacilitates structured multi-agent debates with arguments, rebuttals, and judgments across multiple rounds, enabling diverse AI personas to engage in formal debate and collaborative problem-solving.1717MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover, join, and participate in AgentDebate debates via MCP tools, replacing manual REST orchestration.MIT
- AlicenseNot gradedqualityCmaintenanceEnables running position-driven adversarial debates and code reviews between AI agents via MCP tools, supporting custom positions, multiple rounds, and local CLI models like Claude, Codex, and Gemini.1371MIT
- FlicenseNot gradedqualityBmaintenanceEnables multi-agent debate cross-examination and consensus arbitration through a deterministic, zero-dependency MCP server, providing structured outputs and telemetry for autonomous AI workflows.7-
- AlicenseAqualityBmaintenanceMCP server that reduces confirmation bias in LLMs by orchestrating structured debates between asymmetric context sessions.13MIT
TDQS
C2.9/5.0
Scored across 10 tools
Disambiguation4/5
Each tool has a distinct purpose: session creation, moves, state retrieval, event polling, replay, query processing, relation declaration, relation query, context retrieval, and stats. There is some overlap between `estado` and `ultimos_eventos` (both return events), but the descriptions clearly differentiate full state+log vs. incremental events, so agents can distinguish them effectively.
Naming Consistency2/5
Tool names follow snake_case but mix verb+noun (crear_sesion, procesar_consulta), bare verbs (mover, consultar), bare nouns (estado, stats), and noun phrases (ultimos_eventos, contexto_primado). This inconsistency in syntactic role makes the naming pattern hard to predict for an agent.
Tool Count4/5
With 10 tools, the set covers both session management and term/relation operations without feeling bloated. The scope is well-bounded; each tool adds a distinct capability. Slightly on the higher side but still appropriate for the domain.
Completeness2/5
Core operations are present (create session, move, query state, process queries, declare/query relations), but there are notable gaps: no session listing or deletion, no term/relation listing, no update or delete for relations. These missing CRUD operations would force agents into workarounds or failures.
Maintenance
ActivityMaintained
ResponsivenessNo issues