Skip to main content
Glama

see

Capture a screenshot of a macOS window or an element by ref when the outline can't convey visuals such as canvases, video, images, or charts.

Instructions

Screenshot of a window, or of one element by ref. Only for what the outline can't show: canvases, video, images, charts.

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": {
      "app": "<app>"
    },
    "name": "see"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes
refNo
widthNoMaximum width in pixels (default 960)
windowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the visual capture scope and the exclusion of outline-visible content, but it does not explain permissions, whether screenshots are stored, or other operational effects.

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 short sentences with no wasted wording. The screenshot purpose is front-loaded, and the usage constraint follows immediately.

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?

There are no annotations or output schema, and three of four parameters lack schema descriptions. The description covers scope well but leaves out important operational details such as app and window semantics and ref provenance.

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

Parameters2/5

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

Schema description coverage is only 25%, with just the width parameter documented in the schema. The description adds some meaning by saying ref targets a single element and by mentioning windows, but it does not explain app, window identifier format, or where ref values come from.

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

Purpose4/5

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

The description uses a specific verb, "Screenshot", and names the resources: a window or one element by ref. It also states the narrower purpose versus outline content. It does not explicitly distinguish itself from the sibling "observe" tool, which prevents a 5.

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?

It gives explicit when-to-use guidance: canvases, video, images, and charts that the outline cannot show. This also implies a when-not-to-use rule for anything the outline can represent. No named alternative is provided, so it stops short of full routing guidance.

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