Code Review Assistant
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROQ_API_KEY | No | Your Groq API key (optional if using Ollama) |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| review_codeB | Provides an automated code review including syntax check, explanation, and suggestions. Args: code_snippet: The code snippet string to review. |
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 1 tool
Only one tool exists, so there is no ambiguity. The tool's purpose is clearly defined.
With a single tool, naming consistency is maintained by default. The name 'review_code' is straightforward.
The server has only one tool, which feels thin for a code review assistant. While it covers the main function, additional tools (e.g., for file review or settings) would be expected.
The single tool provides syntax check, explanation, and suggestions, but lacks other common code review features like file input or configurable review settings. The surface is minimal.