Skip to main content
Glama

ZadenWorks

by io.github.ZadenGG

read_page

Extract clean readable markdown/text from any public URL (title, byline, excerpt, body content with nav/ads/scripts stripped). Handles JS-rendered pages. Paid: $0.01 per call in USDC on Base via x402 — call once without x_payment to receive the payment challenge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic http/https URL to read
selectorNoOptional CSS selector to scope extraction to
maxLengthNo
x_paymentNoOptional X-PAYMENT header value from a completed x402 payment. Omit on first call to receive the payment challenge; complete the payment with your x402 wallet tooling, then retry with this set.
includeLinksNo
includeImagesNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the paid nature and payment challenge, but does not explicitly state whether the operation is read-only or if any side effects occur.

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 concise and well-structured, with the core function stated first and the payment mechanism in a separate sentence.

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?

It covers the main function, output type, and payment flow. Since there is no output schema, it does not need to specify return fields, but could mention potential limitations like page size or error conditions.

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 descriptions already cover all parameters. The description adds useful context about the x_payment flow, but does not elaborate on selector, includeLinks, or includeImages beyond the schema.

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 states the action ('Extract'), the resource ('URL'), and the output ('clean readable markdown/text'), differentiating it from raw rendering by specifying stripped navigation/ads/scripts.

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?

It provides some operational guidance on the x402 payment flow, but does not explicitly compare against sibling tools like render_url or extract_tables to indicate when read_page is the preferred choice.

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

All ZadenWorks toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose, from SEO audits to link checking, content comparison, accessibility scans, structured data validation, and claim verification. No two tools overlap in function.

Naming Consistency4/5

Names mostly follow a consistent verb_noun snake_case pattern (audit_seo, check_links, compare_pages). Minor deviations like rank_x402_services and list_rank_categories are slightly less uniform but still readable and predictable.

Tool Count5/5

14 tools cover a broad but focused range of web page analysis and auditing workflows without feeling bloated. The count is well within the ideal 3-15 range for a specialized service.

Completeness5/5

The tool surface is remarkably complete for the domain: covers SEO, sitemaps, links, content, rendering, accessibility, structured data, claims, and monitoring. No critical dead ends or obvious missing operations for typical use cases.

Resources