Skip to main content
Glama
Sign In
Screen Vision MCP Server

Screen Vision MCP Server

by avicuna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

read_screen_text

Extract text from your screen or a specific region using OCR. Optionally specify a region to focus on smaller areas.

Instructions

OCR the screen or a region.

Args: region: Optional region as "x,y,width,height" string

Returns: JSON string with extracted text

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_screen_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.4

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description should disclose behaviors like permissions needed, potential disruptions, or error handling. It only mentions OCR and returns, but nothing about system impact or limitations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and to the point, with no wasted words. However, it lacks structure like bullet points for args/returns, but is still readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple tool with one parameter and an output schema. But missing context on permissions, errors, and differentiation from similar tools makes it less complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description is essential. It explains the region format as 'x,y,width,height', which adds clear meaning beyond the schema's type definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool does OCR on the screen or a region, with a specific verb and resource. It distinguishes itself from siblings like capture_screen (capture only) and understand_screen (interpretation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., understand_screen, analyze_image). The description does not mention prerequisites, permissions, or typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools