ariadne 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_affected_testsA | Get tests affected by code changes. Automatically runs git diff (including uncommitted changes) and analyzes which tests need to be run. Returns a sorted list of test FQNs (fully qualified names). If the diff contains changes outside the analyzed Kotlin sources (build scripts, resources), a note is appended — consider running the full test suite for those changes. |
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 ambiguity. The tool's name and description clearly define its single purpose.
The tool name follows a descriptive verb_noun pattern ('get_affected_tests'), which is consistent with typical MCP naming conventions.
A single tool is borderline for most servers; while it serves a narrow purpose, additional tools for related operations (e.g., running tests) would be expected.
The tool only covers detection of affected tests, but lacks complementary operations like listing all tests, running tests, or configuring the analysis, leaving significant gaps.