bathys

Overview Schema Source Related Servers Discussions Admin

read_url

Read-only

Fetch a web page and extract its main content as clean, readable markdown. Handles JavaScript-rendered pages, strips navigation and ads, and can return only passages relevant to a query.

Instructions

Read one web page; return its main content as clean, budgeted markdown.

JS-rendered pages are handled by a real headless browser. Boilerplate (nav, footer, ads) is stripped; if query is given, only passages relevant to it are returned. Pages are cached — re-reads with a different query are instant and cost no network. Args: url: absolute http(s) URL query: optional focus; return only passages relevant to it max_chars: output character budget (300-50000) refresh: ignore cache and re-fetch the page

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`query`	No
`refresh`	No
`max_chars`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Sep 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The description discloses caching, refresh behavior, JS rendering, and boilerplate stripping, which go beyond the readOnly annotation. It does not mention network costs or rate limits, but the primary side effects are covered.

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 compact and well-structured, with each feature stated in one clear sentence. No redundant information or filler.

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?

Given the output schema and annotations, the description covers the main behavioral aspects an agent needs: content extraction, caching, and refresh. It could be slightly more explicit about edge cases, but overall it is complete enough for typical use.

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?

The schema has good parameter names and defaults, but the description adds only minimal explanation for query and refresh. It does not clarify the exact format of max_chars or how refresh interacts with cache, leaving some semantics implicit.

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 clearly states the tool reads one web page and returns main content as markdown. It distinguishes from siblings like web_search and deep_research, though read_urls is a close sibling that isn't explicitly contrasted.

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

Usage Guidelines3/5

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

The description explains general behavior (JS rendering, boilerplate stripping, caching) and the query parameter's effect, which implies when it might be used. However, it does not explicitly state when to prefer this tool over read_urls or web_search.

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

Deploy Server