Skip to main content
Glama
Sign In
Screen Vision MCP Server

Screen Vision MCP Server

by avicuna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

capture_screen

Capture the full screen with an optional delay for window switching, adjustable monitor selection, and scaling, returning frame data as JSON.

Instructions

Capture the full screen with optional delay for window switching.

Args: delay_seconds: Wait this many seconds before capturing (default: 3) monitor: Monitor index to capture (0 = all monitors, 1+ = specific monitor) scale: Scale factor for resizing (default: 0.5)

Returns: JSON string with captured frame data or error

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": "capture_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNo
monitorNo
delay_secondsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.4

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description discloses optional delay, monitor selection, scale, and return format. It adds context beyond the schema but could mention side effects like permissions.

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?

Front-loaded purpose, then details in a clear list. Slightly verbose with 'Args' and 'Returns' labels, but still efficient.

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

Completeness4/5

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

Covers all parameters and return format. Lacks prerequisites or error condition details, but overall adequate for a screen capture tool with output schema.

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

Parameters5/5

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

Description explains each parameter (delay_seconds, monitor, scale) with defaults and meaning, compensating for 0% schema coverage. Also describes return value.

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 'Capture the full screen' with a specific verb and resource, distinguishing it from siblings like capture_region or capture_window.

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

Usage Guidelines3/5

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

The description implies it's useful for capturing after a delay for window switching, but does not explicitly state when to use this tool over other screen capture tools or when not to use it.

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