Skip to main content
Glama

macos_screen_capture

Capture the primary monitor as an image attachment so you can inspect the current screen and choose the next UI action before moving or clicking.

Instructions

macOS only. Capture the primary monitor and return the screenshot as an image attachment so you can see the current screen and decide what to do. This is your eyes: call it to inspect the UI before acting with macos_mouse_move/macos_mouse_click, dividing the pixel coordinates you read off it by the reported scale to get logical points. Inside the browser, prefer the tab_* tools, which target page elements exactly. Requires Screen Recording and Accessibility permissions (the shared input session grants both up front).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses the permission requirements (Screen Recording and Accessibility) and that the shared input session grants both up front, states the return form (image attachment), and explains the coordinate-scaling rule needed to act on the result. These are exactly the operational facts an agent needs beyond the schema.

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 capability and its scope are front-loaded in the first sentence, followed by purpose, alternative, and prerequisites. It is dense but every sentence carries actionable information; the only mild cost is that four distinct concerns are packed into one paragraph without visual separation.

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

Completeness5/5

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

For a zero-parameter capture tool with no output schema, the description covers what it returns, how to interpret the returned image, what permissions are needed, and when to prefer an alternative. Nothing an agent needs in order to call it correctly is missing.

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 baseline is 4; there is nothing for the description to disambiguate. The coordinate/scale note concerns interpreting the result rather than parameter meaning, so it does not raise or lower this dimension.

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 plus scope: 'Capture the primary monitor and return the screenshot as an image attachment'. It also distinguishes itself from the tab_* siblings by scoping browser work to those tools, so an agent can tell it apart from tab_screenshot without opening either schema.

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 explicit when-to-use guidance ('call it to inspect the UI before acting with macos_mouse_move/macos_mouse_click') and an explicit alternative with its selection condition ('Inside the browser, prefer the tab_* tools, which target page elements exactly'). It also states a platform exclusion ('macOS only').

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