Skip to main content
Glama

debate_code_review

Start a structured 4-round debate code review: an advocate defends the implementation, a critic challenges it, and a judge synthesizes findings into actionable conclusions.

Instructions

Start a debate-style code review for a specific file or change.

Creates a structured 4-round debate where:

  • Advocate defends the current implementation

  • Critic challenges the implementation and proposes improvements

  • Judge synthesizes findings into consensus conclusions and action items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
judgeNoAgent rendering the verdict (default: team-lead)
criticNoAgent challenging the implementation (default: code-reviewer)code-reviewer
team_idNoTeam ID or name (optional, auto-uses active team if empty)
advocateNoAgent defending the implementation (default: backend-architect)backend-architect
file_pathYesPath to the file being reviewed (relative or absolute)
change_descriptionYesBrief description of what changed and why

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so description must carry full burden. Describes the debate structure but lacks details on side effects (e.g., creation of debate session, persistence), permissions, or output specifics. Output schema exists but is not elaborated in the description.

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

Conciseness5/5

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

Extremely concise, front-loaded with purpose, and uses bullet points for clarity. Every sentence adds value.

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

Completeness3/5

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

Explains the debate process but omits details like error handling, prerequisites, or result format. Given the presence of an output schema, the description is adequate but could be more thorough.

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

Parameters3/5

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

Schema coverage is 100% with adequate parameter descriptions. The description adds minimal extra context (e.g., default roles) but does not significantly enhance understanding beyond schema.

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

Purpose5/5

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

Clearly states it starts a debate-style code review for a specific file/change, detailing the 4-round structure with defined roles (advocate, critic, judge). Distinguishes from sibling 'debate_start' by specifying code review context.

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

Usage Guidelines4/5

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

Explicitly describes when to use (for code review) and the process. Does not mention when not to use or alternatives, but the context is sufficiently clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CronusL-1141/AI-company'

If you have feedback or need assistance with the MCP directory API, please join our Discord server