Skip to main content
Glama
linux-computer-use-mcp

linux-computer-use-mcp

by dhakseshr

zoom

Crop a region of the latest screenshot at full resolution to read small text or inspect icons precisely. Input coordinates refer to screenshot pixels, not the crop.

Instructions

Return a full-resolution crop of a region of the latest screenshot (coordinates in screenshot pixels), to read small text or inspect icons precisely. Coordinates for other tools still refer to the full screenshot, not to this crop.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "zoom"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose one genuinely non-obvious trait, that the crop does not redefine the coordinate frame for other tools, plus that resolution is not downscaled. It omits prerequisites (must a screenshot exist first?), what 'latest' means if the screen has changed, and out-of-bounds behavior.

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

Conciseness5/5

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

Two sentences with no waste; the core action is front-loaded and the coordinate-frame caveat follows immediately because it is the highest-risk misunderstanding.

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?

No output schema and no annotations, so the description must define the result itself, which it does (a full-resolution crop image). For a four-required-parameter region tool, only the precondition and boundary behavior are missing.

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

Parameters3/5

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

Schema coverage is 0% and the four parameters have only bare titles, so the description must compensate. It does establish the unit and frame of reference ('coordinates in screenshot pixels'), but leaves the meaning of width/height ambiguous (extent vs. opposite corner) and says nothing about valid ranges or clamping.

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?

States a specific verb and resource: 'Return a full-resolution crop of a region of the latest screenshot.' It also names the motive ('read small text or inspect icons precisely') and implicitly separates itself from the screenshot sibling by describing a crop rather than a capture.

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

Usage Guidelines4/5

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

Gives a clear condition for use ('to read small text or inspect icons precisely') and a crucial caveat that other tools' coordinates still refer to the full screenshot, preventing a common misuse. It stops short of naming an alternative or stating when not to zoom.

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