Test Generator 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 |
|---|---|
| parse_documentB | Read a PDF or DOCX and return plain text. |
| export_scenariosC | Save generated test scenarios into a JSON file and store in memory. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| test_scenario_prompt | Provide a prompt for generating structured test scenarios from user stories. This prompt is used to convert user stories with acceptance criteria into structured test scenarios. The output is expected to be a JSON object with user story details, acceptance criteria, and corresponding test scenarios. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_parsed_documents | List all parsed documents and their text. |
| get_exported_scenarios | List all exported scenario files and their contents. |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one exports generated test scenarios to a file, while the other parses documents to extract text. There is no overlap in functionality or ambiguity between them.
Both tools follow a verb_noun pattern (export_scenarios, parse_document), which is consistent. However, with only two tools, it's a small sample, but there are no deviations in naming style.
With only two tools, the server feels thin for a 'Test Generator' purpose. It lacks core test generation functionality, such as creating or managing test cases, making the scope incomplete and the count too low.
The server is severely incomplete for test generation. It only includes export and parsing tools, missing essential operations like generating tests, editing scenarios, or running tests, which are critical for the domain.