Skip to main content
Glama

dev_capture

Captures the Unflick UI layer for interface inspection, not decoded video frames; use describe_frame for higher-fidelity video frame images from mpv.

Instructions

A picture of the unflick interface. This is the UI layer, not the decoded video: mpv draws on its own surface, which sits above the webview on Windows and below it on macOS and Linux, so no single grab means the same thing on all three. Use describe_frame for the picture itself — it comes from mpv, at higher fidelity than any compositor grab.

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

Input Schema

NameRequiredDescriptionDefault
max_edgeNoLongest edge of the returned image in pixels. Default 768.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 behavioral burden. It usefully discloses platform-dependent compositor behavior and fidelity differences versus describe_frame, but it does not state whether the operation is read-only, what format the image is returned in, or any permission/runtime constraints.

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 explanation is reasonably front-loaded: it first states that this is a UI-layer picture, then justifies platform caveats and points to the higher-fidelity alternative. The platform sentence is long but earns its place by explaining why capture behavior is not uniform across OSes.

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?

For a one-parameter capture tool with no output schema, the description covers the key distinction from decoded video, the platform caveat, and the preferred alternative for high-fidelity frames. It is nearly complete, though the exact output artifact type is left to inference.

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?

The sole max_edge parameter already has a complete schema description explaining that it sets the longest edge of the returned image in pixels. The tool description adds no parameter-specific semantics beyond that, so the baseline of 3 is appropriate.

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 identifies the tool as capturing the UI layer rather than decoded video and explicitly distinguishes its output from describe_frame. It is specific about the resource being captured, though it never uses a direct verb like "captures" and leaves the exact returned artifact somewhat implicit.

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 clear routing guidance by telling the agent to use describe_frame for the mpv picture itself, implying dev_capture is for the UI-layer picture. It does not explicitly state a positive "use this when" condition or discuss other nearby screenshot-like siblings such as dev_snapshot.

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