WarpPay402 Gateway

render_screenshot

Read-only

Captures rendered webpage screenshot image data ($0.01 USDC)

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Target website URL to render and capture

Output Schema

Name	Required	Description
`title`	No	Page title
`success`	Yes	Capture status
`screenshotBase64`	No	Base64 encoded PNG screenshot

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 25, 2026

addedInput schema / properties / url / description

Added value: +"Target website URL to render and capture"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "screenshotBase64": {
+      "description": "Base64 encoded PNG screenshot",
+      "type": "string"
+    },
+    "success": {
+      "description": "Capture status",
+      "type": "boolean"
+    },
+    "title": {
+      "description": "Page title",
+      "type": "string"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

First observedAug 27, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful behavioral fact not present in any structured field: the call costs $0.01 USDC. It still says nothing about latency, rendering timeouts, or failure modes.

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 short sentence, front-loaded with the action and resource, with the cost appended rather than padding the sentence. No wasted words.

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 single-parameter tool with an output schema and rich annotations, the definition covers what it does and what it costs. The missing piece is routing guidance against the numerous web-fetching siblings, which is a real but modest gap.

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 description coverage is 100% with a single documented 'url' parameter, so the schema fully carries the parameter burden and the description adds no syntax or format detail. Baseline 3 applies.

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+resource ('Captures rendered webpage screenshot image data'), and the phrase 'screenshot image data' differentiates it from text-returning siblings like web_scraper and browser_scraper. It does not name those siblings explicitly, so it falls just short of a 5.

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?

No guidance on when to choose this over browser_scraper or web_scraper, which are the obvious alternatives in the sibling list. The only usage-adjacent signal is the price, which implies a paid call, but there is no stated condition for using it.

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

All WarpPay402 Gateway 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?