WebEvalAgent MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPERATIVE_API_KEY | Yes | Your API key from operative.sh |
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 |
|---|---|
| web_eval_agentA | Evaluate the user experience / interface of a web application. This tool allows the AI to assess the quality of user experience and interface design of a web application by performing specific tasks and analyzing the interaction flow. Before this tool is used, the web application should already be running locally on a port. Args: url: Required. The localhost URL of the web application to evaluate, including the port number. Example: http://localhost:3000, http://localhost:8080, http://localhost:4200, http://localhost:5173, etc. Try to avoid using the path segments of the URL, and instead use the root URL. task: Required. The specific UX/UI aspect to test (e.g., "test the checkout flow", "evaluate the navigation menu usability", "check form validation feedback") Be as detailed as possible in your task description. It could be anywhere from 2 sentences to 2 paragraphs. headless_browser: Optional. Whether to hide the browser window popup during evaluation. If headless_browser is True, only the operative control center browser will show, and no popup browser will be shown. Returns: list[list[TextContent, ImageContent]]: A detailed evaluation of the web application's UX/UI, including observations, issues found, and recommendations for improvement and screenshots of the web application during the evaluation |
| setup_browser_stateA | Sets up and saves browser state for future use. This tool should only be called in one scenario:
Launches a non-headless browser for user interaction, allows login/authentication, and saves the browser state (cookies, local storage, etc.) to a local file. Args: url: Optional URL to navigate to upon opening the browser. ctx: The MCP context (used for progress reporting, not directly here). Returns: list[TextContent]: Confirmation of state saving or error messages. |
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 2 tools
The two tools have completely distinct purposes with no overlap. setup_browser_state handles browser authentication and state saving, while web_eval_agent performs UX/UI evaluation of web applications. An agent would never confuse these tools as they serve different phases of the workflow.
Both tools follow a consistent verb_noun pattern with snake_case naming. setup_browser_state and web_eval_agent use clear action-oriented verbs followed by descriptive nouns, creating a predictable naming convention throughout the server.
With only 2 tools, this server feels severely under-equipped for its apparent purpose of web evaluation. A comprehensive web evaluation system would typically need tools for navigation, interaction simulation, accessibility testing, performance measurement, and result analysis beyond just setup and evaluation.
The tool surface is severely incomplete for web evaluation. While setup and evaluation are covered, there are significant gaps: no tools for configuring evaluation parameters, managing browser sessions, analyzing results programmatically, testing specific components, or handling different evaluation methodologies. The server provides only basic endpoints without supporting the full evaluation workflow.