screenshot-feedback-hook-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| take_screenshotA | 截取屏幕并返回图片，用于查看自己刚产出的真实画面（前端页面、EDA/CAD 图等）。 Args: monitor: 0=所有显示器拼接（默认），1..N=指定单个显示器。 不确定编号时先调 list_monitors。 |
| list_monitorsA | 列出可用显示器编号与分辨率，供 take_screenshot 选择 monitor 参数。 |
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 clearly distinct purposes: one lists available monitors, the other takes screenshots. There is no overlap or ambiguity.
Both tools use consistent snake_case naming (list_monitors, take_screenshot), following a clear verb_noun pattern.
With only 2 tools, the server is minimal but well-scoped for its specific purpose of screenshot feedback. It is on the lower end of the ideal range but not inappropriate.
The tool set covers the essential workflow: checking available monitors and taking screenshots. No obvious gaps for the stated use case.