Skip to main content
Glama

code_review

Analyze code or diffs using two parallel LLM reviewers to identify context-blind errors and improve code quality.

Instructions

Review a code snippet or diff using two LLM reviewers in parallel.

At least one of code or paths must be provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoThe code snippet or diff to review. Pass a meaningful amount of code for a useful review. Required unless `paths` is provided (both can also be provided together).
pathsNoFile paths to source files to review. Pass either: a list of paths (e.g. ['src/main.py', 'src/utils.py']), a newline-separated string of paths, or a JSON array string. Paths are relative to the current working directory; absolute paths also work. Files are read automatically from disk. Required unless `code` is provided (both can also be provided together).
contextNoAdditional guidance for the reviewer (e.g., review goals, known issues, areas to focus on, style conventions, constraints). Max 10,000 characters.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions parallel reviewers but lacks details on determinism, error handling, rate limits, or what happens to existing data. This is a significant gap for a tool running multiple LLM calls.

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?

The description consists of two concise sentences, with the purpose front-loaded in the first sentence. No redundant information is present; every sentence earns its place.

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?

Given the output schema exists, the description is somewhat complete but could mention that the output includes review comments from both reviewers. It lacks guidance on when to use this tool and missing behavioral details, but overall it is adequate for a simple tool.

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

Parameters4/5

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

Schema description coverage is 100%, and each parameter has detailed descriptions explaining formats and constraints. The description adds value by explicitly stating the mutual exclusivity condition (at least one required), which is already implied but reinforced.

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?

The description clearly states the action ('Review'), the resource ('a code snippet or diff'), and the method ('using two LLM reviewers in parallel'). It distinguishes from the sibling tool 'system_design_review', which focuses on a different domain.

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

Usage Guidelines3/5

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

The description mentions the prerequisite that at least one of 'code' or 'paths' must be provided, but it does not explicitly state when to use this tool versus alternatives, nor does it provide any exclusion criteria. The implied usage is clear, but guidance is minimal.

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/Shelpuk-AI-Technology-Consulting/lad_mcp_server'

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