Skip to main content
Glama

screenshot

Captures the current video frame and saves it as an image file, with an optional output path for organizing or sharing stills.

Instructions

Take a screenshot of the current video frame

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

Input Schema

NameRequiredDescriptionDefault
outputNoOutput file path (optional, auto-generated if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and leaves significant gaps: it doesn't say whether a file is written to disk or an image is returned inline, what image format or resolution to expect, whether it pauses playback, or whether it has any side effects. The only behavioral hint is indirect, via the optional 'output' path parameter in 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?

A single front-loaded sentence with no filler or repetition. It is appropriately brief, though the terseness reflects missing content rather than deliberate economy.

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?

The tool itself is simple (one optional parameter, no nesting, no output schema), so a short description is defensible. However, with no annotations and no output schema, the definition leaves the agent guessing about the return value (file path? image data?) and the resulting file format, which are the key facts needed to chain this tool with others.

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% and the single optional 'output' parameter is already documented as "Output file path (optional, auto-generated if omitted)". The description adds no additional semantics beyond the schema, so the baseline of 3 for high-coverage schemas applies.

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?

"Take a screenshot of the current video frame" states a specific verb (take a screenshot) and a specific resource (the current video frame), which is clear enough for an agent to act on. It does not, however, distinguish itself from adjacent siblings such as describe_frame or dev_capture, which an agent could plausibly confuse with frame capture.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no when-not-to-use, and no named alternative. The phrase "current video frame" implies it operates at the playback position, but the definition never says how it differs from describe_frame (which presumably also reads the current frame) or from dev_capture.

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