Ndlovu 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| review-local-changesA | Analyze and review uncommitted code changes using AI and static analysis. Performs comprehensive code review including linting, style checks, logic analysis, and security review. Use this when user asks to review, analyze, check, or examine code changes, diffs, or local modifications. |
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'review-local-changes' follows a clear verb_noun pattern.
A single tool is too few for a server named 'Ndlovu Code Reviewer', which suggests a broader scope of code review operations. The tool covers comprehensive analysis, but lacks supporting tools like reviewing committed changes, managing reviews, or handling specific review aspects separately.
The tool surface is severely incomplete for a code review domain. It only handles uncommitted changes, missing obvious gaps such as reviewing committed code, pull requests, historical changes, or providing feedback management, which are essential for a full code review workflow.