Skip to main content
Glama
devatraj

AI-Code-Reviewer

by devatraj

review_diff

Review a code diff for compliance with repository conventions, using RAG over indexed code and docs. Automatically computes git diff if not provided.

Instructions

Review a diff against this repo's own conventions, grounded via RAG over its indexed code/docs/config (run index_repo first). If diff is omitted, computes git diff base_ref..head_ref in repo_path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
diffNo
base_refNoHEAD~1
head_refNoHEAD
repo_pathYes
max_findingsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYes
findingsYes
trace_idYes
hunks_reviewedYes
duration_secondsYes
findings_suppressed_by_criticYes
Behavior3/5

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

No annotations provided, so description carries burden. Explains RAG mechanism and diff omission behavior, but lacks details on findings output, default max_findings, and interaction with index state.

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?

Two concise sentences with front-loaded key action. No redundant information.

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

Completeness4/5

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

Explains core behavior and prerequisite. With output schema present, need not describe return values. Could add more about findings semantics, but overall sufficient.

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?

0% schema coverage; description explains diff omission and names parameters, but does not elaborate on base_ref, head_ref, or max_findings beyond defaults.

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 reviews a diff against repo conventions via RAG. Explains fallback behavior when diff is omitted. Distinct from siblings.

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?

Mentions prerequisite to run index_repo first. Does not explicitly state when not to use, but context distinct from sibling tools.

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/devatraj/AI-Code-Reviewer'

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