Render a JavaScript page in a real browser; returns rendered HTML, text, optional screenshot. (browser; $0.02/call in USDC via x402, 10 free/day).
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Target URL or hostname. | |
| full_page | No | ||
| screenshot | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that it uses a real browser, returns specific outputs, and costs money. However, it does not mention timeouts, resource limits, or error handling behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that packs purpose, output types, and pricing. It is efficient but could be slightly clearer by separating pricing info or adding bullet points for readability.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 16 sibling tools, more context is needed. The description distinguishes by mentioning real browser and specific outputs, but lacks guidance on when to use this vs. others, and does not fully describe return value structure (e.g., format of HTML/text).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 33% (only url has description), and the description only adds that url is a target URL/hostname. The full_page and screenshot parameters are not explained; the description hints at screenshot via 'optional screenshot' but gives no details on usage or effect.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool renders a JavaScript page in a real browser and returns rendered HTML, text, and an optional screenshot. This specific verb-resource combination distinguishes it from siblings like screenshot_page or extract_content, which have different outputs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes pricing and free tier info, but lacks explicit guidance on when to use this tool versus alternatives such as screenshot_page or extract_content. It does not mention prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes, but there are overlapping pairs: unfurl_url/get_oembed/find_favicon all provide URL metadata, and render_page/screenshot_page both render a page (render_page can also screenshot). Descriptions help disambiguate, so only minor confusion is likely.
Tool names mix verb_noun patterns (check_domain, extract_content) with noun_verb patterns (dns_lookup, ssl_lookup, whois_lookup). Additionally, guard_inspect and guard_tx deviate from the typical verb-first style. The naming is readable but not consistent.
With 19 tools, the server is at the heavier end of the scale. While it covers a broad web-intel toolkit, several tools feel out of place for a 'fetcher' (e.g., generate_qr, guard_tx, guard_inspect), making the set feel bloated and unfocused.
The core web-fetching and analysis surface is well covered: DNS, WHOIS, SSL, headers, content extraction, rendering, screenshots, feeds, embeds, redirects, and robots. Missing is a simple raw HTML fetcher, but extract_content and render_page likely cover most needs. The addition of security and utility tools doesn't fill obvious gaps.
