QuickBuild token-saver tools + x402

URL to compact Markdown (free)

url_to_markdown

Read-onlyIdempotent

[FREE] Fetch a public web page and return only its main content as compact Markdown (headings, lists, links, images; scripts/styles/nav/header/cookie banners/footer/ads stripped). Does NOT execute JavaScript. JS-empty, challenge/blocked, invalid or private URLs return 4xx/5xx JSON with error.code, hint, charged:false. Reports original vs output size and estimated tokens saved. No LLM. Limit 30/hour per IP.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Public http(s) URL
`max_chars`	No	Max Markdown chars (default 20000, 500-200000)

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 29, 2026

removedInput schema / properties / maxChars

Removed value: -{
-  "description": "Truncate markdown to this many characters (default 50000)",
-  "maximum": 200000,
-  "minimum": 500,
-  "type": "integer"
-}

addedInput schema / properties / max_chars

Added value: +{
+  "description": "Max Markdown chars (default 20000, 500-200000)",
+  "type": "integer"
+}

changedInput schema / properties / url / description

Previous value: -"Public http(s) URL (hostname, not IP). Private/reserved addresses are refused. Optional: defaults to https://example.com."New value: +"Public http(s) URL"

changedInput schema / required

Previous value: -[]New value: +[
+  "url"
+]

First observedOct 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With annotations already declaring readOnly/openWorld/idempotent/non-destructive, the description still adds substantial behavior: no JavaScript execution, the 4xx/5xx JSON error shape with error.code, hint, and charged:false, size/token-savings reporting, no LLM involvement, and a stated rate limit of 30/hour per IP. Only minor gaps remain, such as pagination of long pages beyond max_chars and whether truncation is flagged as an error.

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?

Three dense sentences, front-loaded with the operation and output format, followed by failure modes and limits. Every clause carries information an agent needs (JS limitation, error contract, cost, rate limit) with no filler.

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?

Absent an output schema, the description fully carries the return-value burden: it describes the Markdown payload, what is removed, the error JSON fields, and the size/token report. Combined with the disclosed rate limit and authentication-free posture, an agent has everything needed to call it correctly and interpret both success and failure.

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 coverage is 100%, so both 'url' and 'max_chars' are already documented in the input schema. The description reinforces that the URL must be public and http(s) (private URLs fail) and that output size is reported, but adds no format or boundary detail for max_chars beyond the schema's own 500-200000 range, so the baseline 3 applies.

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 and resource ('Fetch a public web page') plus a precise output contract ('only its main content as compact Markdown'), then enumerates what is stripped and what element types are preserved. That level of output specificity inherently separates it from sibling tools like screenshot_url, page_metadata, or extract_links_and_headings without needing to name them.

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?

Usage context is implied rather than stated: 'Does NOT execute JavaScript' and the '[FREE]' tag signal static, public pages and a cheap pathway, but no sibling alternative is named for JS-rendered pages or link-only extraction. An agent can infer suitability but is not explicitly routed to another tool.

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

All QuickBuild token-saver tools + x402 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?