mcp-screenshot
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 |
|---|---|
| captureA | Captures a screenshot of the specified region and performs OCR. Options:
|
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'capture' has a clearly defined and distinct purpose.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'capture' is clear and descriptive.
One tool is too few for most server purposes, as it limits functionality and flexibility. While the tool is feature-rich with options, a single tool feels thin and may not cover all potential use cases for a screenshot utility.
The tool provides core screenshot and OCR functionality, but there are notable gaps such as no tools for managing saved screenshots (e.g., list, delete), adjusting OCR settings, or handling different output formats beyond the provided options. The surface is functional but incomplete.