Skip to main content
Glama

Screenshot the open page

tor_screenshot
Read-only

Captures a PNG screenshot of the page currently opened by tor_browse. Set fullPage to true to capture the entire scrollable page instead of the viewport.

Instructions

Take a PNG screenshot of the page opened by tor_browse.

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

Input Schema

NameRequiredDescriptionDefault
fullPageNoCapture the whole scrollable page (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value by naming the output format (PNG) and the dependency on tor_browse state, but says nothing about how the image is returned (inline data vs. path), its size, or failure behavior when no page is loaded.

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?

One sentence, front-loaded with the action and the target, with zero filler. Nothing could be removed without losing information.

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?

For a simple capture tool with a fully documented parameter and annotations covering its safety profile, the essentials are present. However, with no output schema the description should at least hint at the return form of the screenshot and what happens on failure, which it does not.

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 100% and the single parameter fullPage is documented in the schema with its default, so the schema carries the load. The description adds no meaning beyond it, which is the baseline case for a one-parameter tool.

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 ("Take a PNG screenshot") and a precisely scoped resource ("the page opened by tor_browse"), so the agent knows exactly what is captured and on what state it depends. It does not explicitly contrast with tor_archive or tor_fetch, so it falls short of full sibling differentiation.

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?

The phrase "the page opened by tor_browse" implies the required ordering precondition, which is useful. There is no explicit when-not guidance, no mention of behavior when no page is open, and no statement about how this differs from saving page content via tor_archive.

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