Skip to main content
Glama

Screenshot

take_screenshot
Read-onlyIdempotent

Captures the primary screen and displays it on an approval card, letting the PC owner approve or deny sharing the image.

Instructions

Capture the primary screen (1440px JPEG) and show it to the PC owner on a dedicated approval card with the exact preview image. The image leaves the PC ONLY if the owner approves (once or via a grant). Always asks unless an active grant exists. Pass a short "description" of why you need this screenshot: it is burned as a caption into the archived copy when the owner enabled screenshot archiving.

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

Input Schema

NameRequiredDescriptionDefault
noteNoShort human-readable explanation (1 line, in the user's language) of what you are about to do and why. Shown to the user on the approval card. Always provide when calling mutating tools.
agentNoShort consistent identifier or display name of this agent (e.g. 'Claude · Лендинг', 'Тесты', 'Мой агент'). Used to separate tasks and route tray messages when multiple agents work in parallel.
descriptionNoWhy you need this screenshot, in the user's language (1-2 sentences). Saved as a caption on the archived copy when the owner enabled screenshot archiving; falls back to the card note when empty.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: a dedicated approval card with an exact preview, a strict privacy gate ('The image leaves the PC ONLY if the owner approves'), and grant-based reuse. The approval round-trip is a side effect that readOnlyHint/idempotentHint do not convey, so this context matters. It could still say what happens on denial or how long grants last.

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?

Front-loaded with the action and result, then the privacy constraint, then the parameter hint — a sensible order with no filler. The final sentence largely duplicates the schema's own description text, so it does not fully earn its place.

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?

Good coverage of the privacy/approval model for a no-output-schema tool. Gaps remain for a capture tool: whether multi-monitor setups are handled, what a denial returns to the agent, and whether repeated calls within a grant produce fresh captures.

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 description coverage is 100%, so all three parameters are already documented, including the caption and note fallback semantics. The closing sentence repeats the schema's description field almost verbatim, adding emphasis but no new meaning. Baseline 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?

States a specific verb and resource plus output format: 'Capture the primary screen (1440px JPEG)'. An agent immediately knows what it gets back. It stops short of naming a contrast sibling (e.g., read_image for existing files), so differentiation is implicit rather than explicit.

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

Usage Guidelines3/5

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

Gives a real usage condition — 'Always asks unless an active grant exists' — which tells the agent to expect an approval round-trip. However, it never says when to prefer this over alternatives such as read_image or run_command for other capture paths, and never states what to do if approval is denied.

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