Agent Read Proxy

by dev.workers.agent-read-proxy.agent-read-proxy

read_rendered_page

Like /v1/read, but loads the page in a real browser first, so content built by JavaScript (online shops, web apps, single-page sites) is included. Use it when /v1/read comes back empty or incomplete. Returns the readable text or Markdown plus metadata. Price: $0.005 USDC (x402).

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Public http(s) web page
`format`	No	text (default) or markdown

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden of explaining its operational behavior, specifically mentioning that it uses a 'real browser' to handle complex, JavaScript-heavy websites. It also provides non-technical behavioral context like pricing.

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 description is highly efficient, front-loading the primary distinction (JS rendering capability) and followed by clear usage criteria and metadata (pricing).

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?

The description is complete enough for an agent to understand exactly when this specialized tool is required over the standard page-reading siblings.

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?

Even though schema coverage is 100%, the description adds value by clarifying the output formats ('readable text or Markdown plus metadata') and detailing the operational requirements of the service (real browser loading).

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 clearly distinguishes itself from sibling tools (specifically '/v1/read' is cited) by explaining that it loads the page in a real browser to handle JavaScript content.

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?

It provides explicit guidance on when to use the tool ('Use it when /v1/read comes back empty or incomplete'), making it a highly precise instruction for agent decision-making.

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

All Agent Read Proxy 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?