Capture a screen region and extract text with OCR, turning any on-screen content into selectable, copyable text.
Capture screen and extract text using OCR
| Name | Required | Description | Default |
|---|---|---|---|
| region | No | Optional region to capture. If not provided, captures full screen |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the high-level behavior (screen capture + OCR) and omits important traits such as the return format, permission requirements, coordinate system for the region, or whether any temporary files are created.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single focused sentence that front-loads the action and includes the key differentiator (OCR). There is no filler or redundancy; every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of an output schema and annotations, the description is incomplete. It does not specify what the OCR output looks like, how region coordinates relate to the screen, or any side effects and permissions, leaving an agent with significant uncertainty about the tool's full behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool description adds no parameter-level meaning beyond the schema, but the schema itself fully documents the only parameter, region, including its optionality and default behavior. With 100% schema description coverage, the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear action: capture the screen and extract text using OCR. It names the resource (screen) and the operation (OCR text extraction), which distinguishes it from the capture-only sibling tools, though it does not explicitly contrast with them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to choose this tool over alternatives like capture_region or find_text_on_screen. The description only implies use when text extraction is needed, with no explicit context, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.