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

linux-computer-use-mcp

by dhakseshr

screenshot

Captures the entire display and returns an image with pixel coordinates used by other desktop-control tools.

Instructions

Capture the whole screen. Use the returned image's pixel coordinates for every other tool. Most action tools already return a fresh screenshot, so you rarely need this.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the output is an image, that it covers the entire screen, and that its pixel space is the shared coordinate system for sibling tools — non-obvious behavior worth stating. Gaps remain on multi-monitor setups, image resolution/scaling, and whether it requires any permission or focus state.

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?

Three short sentences, zero filler, with the core action front-loaded and the usage caveat following immediately. Every sentence carries distinct information.

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 exists, so the description must characterize the return value; it does so at a high level (an image whose pixel coordinates drive all other tools). For a parameterless tool this is nearly sufficient, though image format, dimensions, and multi-display behavior are left unstated.

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?

The tool takes zero parameters, so the schema baseline applies; there is nothing parameter-level to explain. The description instead spends its space on the return-value semantics, which is the right allocation.

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 ('Capture the whole screen') and scopes it to the full screen rather than a region or window. It also carves out its niche against sibling action tools that return screenshots themselves, so the agent can pick it apart from click/scroll/type_text.

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

Usage Guidelines5/5

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

Gives an explicit when-not ('Most action tools already return a fresh screenshot, so you rarely need this') plus the downstream contract ('use the returned image's pixel coordinates for every other tool'). An agent knows both when to reach for it and what to do with the result.

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