MCP-Allure
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 |
|---|---|
| get_allure_reportC | read allure report and return json data |
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 'get_allure_report' has a single, clearly defined purpose of reading Allure reports and returning JSON data.
The single tool name 'get_allure_report' follows a clear verb_noun pattern (get + report). Since there is only one tool, consistency is inherently perfect with no deviations to assess.
The server has only one tool, which feels thin for a reporting domain like Allure. A single tool for reading reports lacks essential operations such as generating, listing, or managing reports, making it under-scoped for typical use cases.
The tool surface is severely incomplete for an Allure reporting server. It only provides a 'get' operation for reports, missing critical functions like creating reports, listing available reports, updating report data, or deleting reports, which are essential for full lifecycle coverage.