Lucidity MCP
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 |
|---|---|
| analyze_changesA | Prepare git changes for analysis through MCP. This tool examines the current git diff, extracts changed code, and prepares structured data with context for the AI to analyze. The tool doesn't perform analysis itself - it formats the git diff data and provides analysis instructions which get passed back to the AI model through the Model Context Protocol. Args: workspace_root: The root directory of the workspace/git repository path: Optional specific file path to analyze Returns: Structured git diff data with analysis instructions for the AI |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_changes | Generate a prompt for analyzing git code changes via MCP. This function creates a structured prompt that will be passed back to the AI model through the Model Context Protocol, guiding it to analyze git changes effectively. Args: code: The changed code to analyze language: The programming language of the code original_code: The original code before changes (optional) Returns: A formatted prompt for the AI to analyze git changes |
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 'analyze_changes' has a clearly defined and distinct purpose of preparing git changes for analysis, making it impossible to confuse with other tools.
The single tool name 'analyze_changes' follows a clear verb_noun pattern (analyze + changes). Since there is only one tool, there is no inconsistency to evaluate, and the naming is straightforward and descriptive.
A single tool is too few for most practical server purposes, as it limits functionality and scope. While the tool is well-defined, a server with only one tool feels thin and incomplete for handling git analysis or broader tasks, indicating a mismatch in scope.
The server's domain appears to be git change analysis, but with only one tool that prepares data without performing analysis, there are significant gaps. Missing operations like actual analysis, history review, or commit management make the surface severely incomplete for the inferred purpose.