Gemini Code Reviewer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gemini_code_reviewC | Use Gemini CLI to review code for correctness, best practices, and improvements |
| gemini_analyze_codeC | Use Gemini CLI to analyze and explain code functionality |
| gemini_suggest_improvementsC | Use Gemini CLI to suggest specific improvements for code |
| gemini_validate_architectureC | Use Gemini CLI to validate code architecture and design patterns |
| get_review_historyA | Get the history of operations performed in this session |
| gemini_propose_planA | Use Gemini CLI to generate a detailed implementation plan for another AI to follow. This tool creates structured, step-by-step plans that can be executed by Claude or other AI assistants. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The gemini_code_review, gemini_analyze_code, and gemini_suggest_improvements tools overlap heavily, as code review typically includes analysis and improvement suggestions. While gemini_validate_architecture and gemini_propose_plan are distinct, the three overlapping tools create boundary ambiguity.
Naming is inconsistent: get_review_history uses a get_ prefix while the rest use gemini_, and the verb/noun structure varies (gemini_code_review is noun-led, while others are verb-led like gemini_analyze_code). No uniform verb_noun pattern is applied.
Six tools is a well-scoped set for a code review server, covering review, analysis, suggestions, architecture validation, and planning without excess.
The tool set covers the core lifecycle of code review (review, analyze, improve, validate architecture, plan). Minor gaps exist such as a dedicated security review or merge/reporting capability, but these do not critically undermine the domain.