Skip to main content
Glama

Screenshot a page, through a simulation

pour_screenshot

Captures a PNG of a web page as loaded or with an accessibility simulation applied, so you can inspect colour-vision, low-vision, focus, and landmark rendering.

Instructions

A PNG of the page as loaded, or as seen through one of pour's simulations, the same ones the extension ships. Vision: cataract (Clouded Lens), presbyopia (Near-Vision Loss), lowAcuityMild (Slight Defocus), lowAcuity (Uncorrected Focus), lowAcuityStrong (Significant Defocus), lowAcuityHeavy (Severe Defocus), lowLight (Dim Environment), lowContrast (Reduced Contrast), retinitisRing (Ring Loss), glaucoma (Tunnel Vision), glaucomaLarge (Tunnel Vision (Large)), macularDegeneration (Central Vision Loss), macularDegenerationLarge (Central Vision Loss (Large)), diabeticRetinopathy (Patchy Vision), nystagmus (Involuntary Eye Movement), hemianopiaLeft (Left Field Loss), hemianopiaRight (Right Field Loss), amblyopia (Reduced Acuity (One Eye)), afterimages (Afterimages), ageSlider (Age Slider), scotopicRose (Rose Tint), scotopicYellow (Yellow Tint), scotopicAqua (Aqua Tint), protanopia (Red Absent (Protanopia)), deuteranopia (Green Absent (Deuteranopia)), tritanopia (Blue Absent (Tritanopia)), achromatopsia (Monochromacy), protanomaly (Red Deficiency), deuteranomaly (Green Deficiency), tritanomaly (Blue Deficiency). Sensory, motor and structure: lightSensitivity (Light Sensitivity (Metaphor)), colourHypersensitivity (Colour Hypersensitivity (Metaphor)), motionSensitivity (Motion Sensitivity (Metaphor)), hyperfocusTunnel (Hyperfocus Tunnel (Metaphor)), attentionFragmentation (Attention Fragmentation (Metaphor)), peripheralDistraction (Peripheral Distraction (Metaphor)), detailFixation (Detail Fixation (Metaphor)), processingDelay (Processing Lag (Metaphor)), sensoryInterference (Sensory Interference (Metaphor)), sensorySpike (Sudden Sensory Spike (Metaphor)), dyslexiaVisualStress (Visual Stress (Pattern Glare) (Metaphor)), dyslexiaCrowding (Crowding Effect), dyslexiaTrackingLoss (Tracking Loss (Metaphor)), dyslexiaWashout (Letter Instability (Metaphor)), dyslexiaContrastSensitivity (Contrast Sensitivity), handTremor (Hand Tremor), handTremorStrong (Hand Tremor (Strong)), restingTremor (Resting Tremor), ataxicDrift (Ataxic Drift), pointerSpasm (Sudden Jerk), pointerHidden (Hidden Pointer (Keyboard Only)), fingertipTouch (Fingertip Touch), forcedColours (Forced Colours (Windows Contrast Theme)), screenMagnifier (Screen Magnifier (400%)), textSpacing (Text Spacing), focusOrder (Focus Order), landmarkMap (Landmarks & Headings). Omit the filter for the page as it is. Useful for what the numbers cannot show: colour-vision and low-vision rendering, and the focusOrder and landmarkMap lenses drawn over the page.

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

Input Schema

NameRequiredDescriptionDefault
urlNoThe page to load, http or https only. A local dev server is fine (http://localhost:8080/). Without a scheme, https is tried first, then http. For a file on disk use path instead: file:// URLs are refused.
pathNoA file on disk to check instead of a URL, relative to the folder the server was started in. It is served over http from its own folder, so relative assets load. Give one of url or path, not both.
rootNoWith path: the folder to serve as the site root, for a page whose assets are addressed from the root (/styles.css) rather than from its own folder. Defaults to the file's own folder.
filterNoA simulation name. Omit for the plain page.
scrollNoScroll through the page first so lazy-loaded content is in the DOM. Changes the numbers, by design. Default false.
waitMsNoExtra settle time after the page loads, in milliseconds. Default 0.
fullPageNoCapture the full page height instead of the viewport. Long pages make large images. Default false.
insecureNoIgnore TLS certificate errors, for a dev server with a self-signed certificate. Default false.
viewportNoViewport as WxH. Default 1440x900. Responsive pages serve different content per width, so the width is part of the result.
timeoutMsNoNavigation timeout in milliseconds. Default 30000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and most of what it could disclose is absent: no statement that this is a non-mutating read of a page, no mention that it drives a browser/network fetch, no failure or timeout behavior. The one genuinely useful disclosure is the return type (PNG) in the absence of an output schema, but otherwise the text is consumed by the filter list rather than behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single run-on sentence carries a several-hundred-word enum dump in the middle, so the reader must wade through the filter catalog to reach the operational sentence at the end. Key facts (PNG output, omit-filter default) are buried rather than front-loaded, and the enum listing duplicates what the schema already enumerates.

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?

With ten parameters fully documented in the schema and no output schema, the description supplies the two things structured fields cannot: the return format (PNG) and the meaning of the filter keys. What is missing for a tool of this complexity is the cost/behavior profile (browser launch, latency, large full-page images) and overlap resolution with pour_focus_order.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description genuinely earns a step above it by mapping bare enum keys to human-readable labels (cataract = Clouded Lens, hemianopiaLeft = Left Field Loss) and grouping them into vision versus sensory/motor/structure categories, which meaningfully aids filter selection. The "Omit the filter for the page as it is" line, however, only repeats the schema's "Omit for the plain page."

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause states the product ("A PNG of the page as loaded, or as seen through one of pour's simulations") but is a sentence fragment that never names the action, leaving the title to supply the verb. The overlap with pour_focus_order is only hinted at in the closing line ("what the numbers cannot show"), so the distinction from siblings is left for the agent to infer.

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 when-to-use / when-not-to-use guidance; the only routing hint is the vague "Useful for what the numbers cannot show." Critically, the description never explains how the focusOrder and landmarkMap lenses relate to the pour_focus_order sibling, which is the most likely wrong-tool choice an agent could make.

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