agenteyes-mcp
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 |
|---|---|
| screenshot_urlB | Open a URL in headless Chromium and return PNG screenshot(s), an accessibility snapshot, and visible page text. |
| get_page_textA | Open a URL in headless Chromium and return the page title, accessibility snapshot, and visible text (no screenshot). |
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 are mostly distinct: screenshot_url includes screenshots, while get_page_text does not. However, both return accessibility snapshots and visible text, creating some overlap that could lead to arbitrary selection when only text/snapshot is needed.
Both names use snake_case, but verb patterns are inconsistent: 'screenshot' acts as a verb/noun, while 'get_page_text' uses the verb 'get'. The mix is readable but not a predictable pattern.
Two tools is thin for a web content extraction service. While each tool has a role, the surface feels minimal and could benefit from additional focused tools (e.g., raw HTML, links).
Core capabilities (screenshot and text/snapshot) are covered, but notable gaps exist: no way to retrieve raw HTML, page links, or interact with the page. Agents may hit dead ends for structured data extraction.