Skip to main content
Glama

gemini_review

Review files or a git diff to surface concrete issues with file:line locations, severity, and suggested fixes, returning both a written review and structured findings.

Instructions

Have Gemini review files and/or a git diff and list concrete issues (file:line, severity, suggested fix). Returns the written review plus structured findings. Give files, a diff, or both.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gemini_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
diffNoAttach a git diff: "staged" (index vs HEAD), "working" (unstaged), "HEAD" (all uncommitted changes), a ref, or a range like "main...HEAD". Counts against the size limit.
filesNoPaths relative to the project root (max 20 files, 500 KB total). Also accepts line ranges (src/a.ts:40-120), directories (src/) and globs (src/**/*.ts); globs and directories respect .gitignore. Contents are inlined into the prompt.
focusNoOptional focus, e.g. "security", "performance", "readability".
modelNoModel ID as listed by `agy models`; the suffix is the reasoning effort, e.g. gemini-3.8-flash-low | -medium | -high. Omit to use the configured default (.zwilling.json, else agy's). Higher effort is slower.
timeout_sNoTimeout for this call in seconds (default 120).

Output Schema

NameRequiredDescriptionDefault
parsedYesFalse if Gemini's answer had no parsable findings block; then `findings` is empty.
findingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The only annotation is openWorldHint=true, so the description carries most of the burden. It usefully discloses the output shape (written review plus structured findings) and the issue format (file:line, severity, fix), but says nothing about cost, latency, failure modes, size limits, or what happens when a diff range cannot be resolved.

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?

Three short sentences, front-loaded with the action and the deliverable, then the return value, then the input contract. Nothing is repeated and nothing is padding.

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?

With an output schema present and full parameter coverage, the description only needs to frame purpose and input contract, which it does. The missing piece for a tool at this complexity is routing guidance relative to ask_gemini and any expectation about runtime or model selection trade-offs.

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 coverage is 100%, so baseline is 3, but the description adds a genuinely non-obvious constraint: at least one of files or diff must be supplied even though required parameters is 0. That combination guidance is not derivable from the schema alone.

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

Purpose4/5

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

Names a specific verb and resource: Gemini reviews files and/or a git diff and lists concrete issues with file:line, severity, and suggested fix. It is distinguishable from asks/patch siblings by name and framing, but it never explicitly contrasts itself with ask_gemini, so it stops short of full sibling differentiation.

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?

'Give files, a diff, or both' tells the agent what input combination is acceptable, which implicitly frames the usage. There is no explicit when-to-use vs when-to-use-an-alternative guidance and no exclusions or prerequisites.

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