Skip to main content
Glama

Tollkit

by io.github.UltraStarz
OverviewDiscussionsAdmin

Screenshot a web page

screenshot_page
Read-only

Capture how any public web page looks: a 1280x800 JPEG from a real browser, returned as base64 with its SHA-256, the title and the final URL.

Use it to see a page's layout, check that something renders, or hand the image to a vision model. The image is roughly 50-150 KB of base64 in the response.

$0.003 USDC per capture over x402. A page that fails to load or returns an error costs nothing. For signed, timestamped evidence of a page use attest_page instead. Call without payment to get a quote. The first 3 calls a day through this tool server are free (no wallet needed).

When to use: You need to see a page: its layout, whether something renders, or an image for a vision model. Use instead: read_page when you only need the words (smaller and cheaper); attest_page for signed evidence of a page. Parameters: url must be absolute http(s) and public. Returns: a 1280x800 JPEG as base64, its sha256, title and final_url.

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL of a public page.
paymentNoBase64 x402 payment payload. Omit it to receive a quote; sign that and call again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint, but the description adds rich behavioral detail beyond them: cost ($0.003 USDC per capture), no charge for failed loads, first 3 calls/day free, image size (50-150 KB base64), and the quote-then-sign payment sequence.

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 core capability and organized into labeled sections, making it easy to scan. It is somewhat repetitive ('see a page's layout' appears in the opening and again under 'When to use'), costing a bit of tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fully covers return values (JPEG base64, sha256, title, final_url), pricing behavior, and the payment workflow. Nothing an agent needs to invoke it correctly is missing.

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%, so both parameters are already documented in the schema. The description restates url constraints (absolute http(s), public) and the payment quote flow, which the schema already conveys, adding little beyond the structured fields. Baseline 3 applies.

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

Purpose5/5

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

The description names a specific verb and resource ('Capture how any public web page looks') and specifies the concrete output: a 1280x800 JPEG from a real browser with SHA-256, title, and final URL. It clearly distinguishes itself from siblings by routing to read_page and attest_page.

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

Usage Guidelines5/5

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

Explicit 'When to use' and 'Use instead' sections name the exact alternatives (read_page for text, attest_page for signed evidence) and the conditions that select each. The x402 payment flow ('Call without payment to get a quote') and the free-call tier add actionable context.

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

All Tollkit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources