Smart Code Reviewer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TIMEOUT | No | Timeout for code analysis operations in milliseconds | 30000 |
| MCP_LOG_LEVEL | No | Log level for the MCP server | info |
| MCP_MAX_CODE_SIZE | No | Maximum code size that can be analyzed | 50000 |
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 |
|---|---|
| analyze_code_qualityC | 分析代码质量，检测潜在问题和改进建议 |
| generate_documentationC | 为代码生成详细的文档和注释 |
| detect_security_issuesC | 检测代码中的安全漏洞和风险 |
| suggest_refactoringC | 提供代码重构建议，改善代码结构和可读性 |
| calculate_complexityC | 计算代码复杂度指标（圈复杂度、认知复杂度等） |
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 5 tools
Each tool has a clearly distinct purpose with no overlap: code quality analysis, complexity calculation, security issue detection, documentation generation, and refactoring suggestions. An agent can easily differentiate between them based on their specific focus areas.
All tool names follow a consistent verb_noun pattern (e.g., analyze_code_quality, calculate_complexity) using snake_case throughout. The naming is predictable and readable across all five tools.
With 5 tools, this server is well-scoped for a code review domain. Each tool earns its place by covering distinct aspects of code review (quality, complexity, security, documentation, refactoring), avoiding bloat or thinness.
The tool set provides complete coverage for a code review server, addressing key areas like quality analysis, complexity metrics, security scanning, documentation, and refactoring. There are no obvious gaps that would hinder an agent's workflow.