Skip to main content
Glama

web_to_markdown

Fetch a public web page and convert it into clean Markdown with title, byline, and word count, while honoring robots.txt and returning errors for blocked pages.

Instructions

Fetch one public web page and return clean Markdown plus title, byline and word count (Readability extraction; mode=full keeps the whole body). Honors robots.txt and never bypasses logins, paywalls or captchas; blocked pages return an error. Price about $0.02. Paid per call with x402 from your XRPL_SEED wallet (XRP or RLUSD, capped by MAX_*PER_CALL and SESSION_BUDGET*). Without a wallet it returns the price quote and charges nothing. Failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) page URL
modeNo
assetNoAsset to pay with on the XRP Ledger: XRP (default) or RLUSD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses robots.txt compliance, refusal to bypass auth/paywalls/captchas, error behavior on blocked pages, and the full payment model including price, x402/XRPL wallet source, per-call and session caps, quote-only response without a wallet, and no charge on failure. These are exactly the non-obvious traits an agent needs before invoking a paid network fetch.

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?

Front-loads the core action and return format in the first clause, then layers constraints and payment terms in short, information-dense sentences. The pricing and wallet details are long but each sentence carries distinct, decision-relevant information for a paid tool.

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?

Complete on the essentials: outputs are enumerated despite no output schema, blocking behavior is defined, and cost/payment failure paths are spelled out. It omits operational limits such as timeouts, maximum page size or redirect handling, which an agent might want before fetching a large or slow page.

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?

Schema coverage is 67%, below the point where the schema alone suffices, and the description compensates: it clarifies that 'mode=full keeps the whole body' (implying readable is the trimmed default) and ties 'asset' to XRP-or-RLUSD payment from the wallet. The 'url' parameter's public http(s) constraint is reinforced in prose. Minor gap: the default mode value is implied rather than stated.

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?

Names a specific verb and resource ('Fetch one public web page') and states the exact return shape: clean Markdown plus title, byline and word count. It also distinguishes the extraction behavior via 'Readability extraction; mode=full keeps the whole body', so an agent can tell what it gets without opening the schema.

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

Usage Guidelines4/5

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

Gives clear preconditions for use: the page must be public, robots.txt is honored, and logins, paywalls and captchas are never bypassed, with blocked pages returning an error instead. It does not name a sibling tool to use for other cases (e.g. file conversion or non-public content), so routing guidance stops short of explicit alternatives.

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