Skip to main content
Glama

capture

Takes a screenshot of the Miro board window to visually verify changes, optionally zooming to specified item IDs first. Use after batch edits to reduce image token use.

Instructions

Screenshot of the Miro window so you can see the result. Optionally zoom to ids first. Windows only; the board window must not be minimized (it may be behind others). ~1.5k tokens per image, so capture once after a batch of changes, not after every call.

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

Input Schema

NameRequiredDescriptionDefault
idsNo
maxWidthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the Windows-only platform limit, the window-state requirement, and the ~1.5k token-per-image cost that governs call frequency. It stops short of describing failure behavior when the window is minimized or what exactly is returned (full window vs. cropped region).

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 dense sentences with zero filler, leading with what the tool produces before constraints and cost advice. Every clause earns its place — platform limit, window state, token budget all change agent behavior.

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 two-parameter capture tool with no output schema and no annotations, this covers purpose, platform, preconditions, and cost/frequency guidance. The one material omission is maxWidth semantics and any indication of what happens on failure (minimized window, off-screen board).

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%, so the description must compensate and only partly does: 'zoom to ids first' conveys that ids selects items to frame before the shot. The maxWidth parameter (default 1400, range 400–2400) is never mentioned, so its effect on output size is undocumented everywhere.

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?

The description states a specific verb and resource: 'Screenshot of the Miro window,' immediately disambiguating the vague tool name 'capture'. It also contrasts with the zoom-first path ('Optionally zoom to ids first'), so an agent can tell it apart from zoom_to 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?

Explicit when-to-use ('so you can see the result'), an explicit precondition ('board window must not be minimized'), and an explicit when-not ('capture once after a batch of changes, not after every call'), plus a routing hint to zoom first. This is the full when/when-not/alternative set.

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