Skip to main content
Glama
Korrnals

bathys

by Korrnals
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

read_url

Read-only

Extract the main content from any URL as clean markdown, removing boilerplate and handling JavaScript-rendered pages. Filter by query and cache results for fast re-reads.

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 find: search the cached RAW text for this exact substring (case-insensitive): returns matches with counters and context, no network needed. Requires the page to have been read before; combine with query for first reads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
findNo
queryNo
refreshNo
max_charsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / find
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Find"
+}
  2. First observedv0.5.0

TDQS

A4.5/5.0
Behavior5/5

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

With annotations already declaring readOnlyHint and openWorldHint, the description adds substantial behavioral detail: headless browser handling, boilerplate stripping, query filtering, caching with no network on re-reads, and exact find semantics with counters and context. This goes well beyond the annotations and fully discloses side effects like cache usage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and well-organized with a clear intro, a behavior paragraph, and an args list. It slightly repeats 'query' behavior between the intro and the args list, but every sentence earns its place. The front-loaded purpose and structured parameter explanations make it easy to scan.

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?

For a tool with 5 parameters, no schema descriptions, and an output schema available, the description fully equips an agent: it covers parameter semantics, caching, network behavior, and the specific semantics of find. The presence of an output schema means return value details don't need duplication. Nothing necessary for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden. It explains every parameter: url format, query filtering, max_chars budget with range, refresh ignoring cache, and find's case-insensitive exact match with requirements (must have been read before). This adds rich meaning the schema completely lacks.

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 opens with a specific verb+resource: 'Read one web page; return its main content as clean, budgeted markdown.' This clearly differentiates it from sibling tools like read_urls (plural) and web_search. The additional behaviors (JS rendering, boilerplate stripping) make the purpose unmistakable.

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 gives context for when to use parameters (query for relevance, refresh to bypass cache, find for cached text) but never explicitly states when to prefer this tool over siblings like read_urls or web_search. Storage and caching behavior indirectly imply single-page reads, but no alternatives or exclusions are named.

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

Deploy Server

Other Tools