Limetest 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 |
|---|---|
| browser_endtoendC | Run an end to end test suit in the browser |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Page console |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'browser_endtoend' follows a clear snake_case pattern.
One tool is too few for a server's purpose, as it severely limits functionality and suggests an incomplete or trivial implementation. This is a borderline case leaning toward inadequacy.
The server is severely incomplete; with only a single end-to-end test tool, there are obvious gaps in functionality for any meaningful domain, such as setup, teardown, or other testing operations.