Skip to main content
Glama
Sign In
Cat Burglar

Cat Burglar

by DrMkdaddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Screenshot

screenshot
Read-only

Capture a viewport, full page, or single element as PNG and return it inline, with an optional path to save a copy.

Instructions

Capture the viewport, full page, or a single element as PNG. The image is returned inline; an optional path saves a copy under the artifact directory.

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
pathNoSave path relative to the artifact directory.
selectorNoCapture only this element.
full_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description goes beyond that by disclosing the return channel (image inline) and the only side effect (copy saved under the artifact directory when path is given). It stops short of covering failure modes, e.g. what happens with a selector that matches nothing, or any size/timeout limits for full-page capture.

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?

Two sentences, front-loaded with the core action and the selectable scopes, followed by the return/save behavior. No filler, though the save-path clause is compressed to the point of ambiguity about what 'artifact directory' resolves to.

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 three-parameter, no-required-argument read tool with no output schema, the definition covers action, scope options, and return format adequately. Missing only edge-case behavior and a note on when the inline image versus a saved file is preferable.

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 67%, and the one undocumented parameter, full_page, is exactly what the description's 'viewport, full page' phrasing explains, so it does close that gap. However, selector and path semantics are largely restated from the schema rather than extended with format or constraint detail, keeping this at baseline-plus rather than genuinely additive.

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?

Names a specific verb and resource ('Capture ... as PNG') and enumerates the three capture scopes (viewport, full page, single element), which unambiguously identifies the operation. It does not distinguish itself from visually adjacent siblings such as snapshot, pdf, or markdown, so an agent must infer the boundary.

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?

Usage is only implied by the scope enumeration; there is no statement of when to prefer this over pdf, snapshot, or extract, nor any prerequisite or exclusion. An agent can infer 'use for visual capture' but gets no 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