Coding Standards MCP Server
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 |
|---|---|
| list_templatesB | List all available templates grouped by type and language |
| get_style_guideB | Get coding style guidelines for the specified language in Markdown format |
| get_best_practicesB | Get application best practices for the specified language in Markdown format |
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 3 tools
Each tool has a clearly distinct purpose: get_best_practices focuses on application-level best practices, get_style_guide on coding style guidelines, and list_templates on available templates. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern (get_best_practices, get_style_guide, list_templates) with clear, descriptive verbs and nouns. The naming is uniform and predictable across all three tools.
With only 3 tools, the server feels thin for a coding standards domain, which might include operations like validating code, applying templates, or managing standards. While the tools are well-defined, the count is borderline low for the apparent scope.
The tool surface has significant gaps for a coding standards server. It lacks CRUD operations for managing standards (e.g., create/update/delete practices or templates), validation tools, or integration with code analysis, which are core to the domain. This will likely cause agent failures in comprehensive workflows.