Agent Toolbox

Screenshot

screenshot

Read-only

Screenshot of a public web page in a real headless Chrome after it has loaded (JavaScript included): a JPEG of the visible window or the full page, 320 to 1920 pixels wide, as base64. Costs USD 0.003 per call, paid with x402 (USDC on Base); calls that fail are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "screenshot"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	A public http(s) URL
`width`	No	Window width in pixels (default 1280)
`full_page`	No	The whole page instead of the first screen (default false)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent false, and destructive false. The description adds useful behavioral context beyond annotations: JavaScript is rendered, output is JPEG base64, and billing is USD 0.003 per call with failed calls not charged.

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?

The purpose is front-loaded in a single dense sentence with no wasted text. Output format, sizing, and billing details are compactly included.

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?

The tool is simple, annotations cover the safety profile, and the schema covers parameters. The description supplies output and cost context despite there being no output schema, though it lacks sibling-oriented usage guidance.

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 schema already documents all three parameters. The description still adds useful meaning by tying width to a 320–1920 pixel range and distinguishing full-page from visible-window capture.

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?

The description states a specific resource and operation: a screenshot of a public web page in headless Chrome after loading, including JavaScript, as JPEG/base64. It clearly distinguishes an image-capture tool from text-oriented siblings by output type, though it does not explicitly name alternatives like read_url or url_to_markdown.

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?

It explains what the tool produces but gives no when-to-use or when-not-to-use guidance. It does not route the agent between screenshot, read_url, url_to_markdown, or other URL-related siblings.

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

All Agent Toolbox tools Inspect

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

Need Help?