x402-data-gateway

Read Web Page as Markdown

read

Fetch a public HTTP(S) page and return its readable body as cleaned Markdown for LLM context, preserving headings, links, and lists while dropping navigation, ads, scripts, headers, footers, asides, and forms. Use extract instead when you need metadata, JSON-LD, Open Graph/Twitter tags, or a link inventory. Markdown is capped at 40,000 characters and no JavaScript is executed. Payment challenge and credentials are bound to GET https://agents.samedaydesk.com/read, not mcp://. Retry the identical authorized arguments and credential.

Input Schema

Name	Required	Description	Default
`url`	Yes	Public HTTP(S) URL whose readable body is needed as Markdown. Content is fetched without JavaScript rendering and may be truncated at 40,000 characters. Check status/sourceOk/error/truncated/capture; missing discussion text is not proof of absence.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`url`	Yes
`error`	Yes
`title`	Yes
`status`	Yes
`capture`	Yes
`finalUrl`	Yes
`markdown`	Yes
`sourceOk`	Yes
`fetchedAt`	Yes
`truncated`	Yes
`wordCount`	Yes
`requestedUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 10, 2026

changedInput schema / properties / url / description

Previous value: -"Public HTTP(S) URL whose readable body is needed as Markdown. Content is fetched without JavaScript rendering and may be truncated at 40,000 characters."New value: +"Public HTTP(S) URL whose readable body is needed as Markdown. Content is fetched without JavaScript rendering and may be truncated at 40,000 characters. Check status/sourceOk/error/truncated/capture; missing discussion text is not proof of absence."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "capture": {
+      "additionalProperties": false,
+      "properties": {
+        "bodyBytes": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "bodyTruncated": {
+          "type": "boolean"
+        },
+        "charset": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "charsetSource": {
+          "enum": [
+            "content-type",
+            "html-meta",
+            "default-utf-8",
+            "invalid-charset-fallback"
+          ],
+          "type": "string"
+        },
+        "javascriptExecuted": {
+          "const": false,
+          "type": "boolean"
+        },
+        "markdownLimitChars": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "maxBodyBytes": {
+          "type": "integer"
+        },
+        "method": {
+          "const": "http-get-no-javascript",
+          "type": "string"
+        },
+        "textExcerptLimitChars": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "textTruncated": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "method",
+        "javascriptExecuted",
+        "maxBodyBytes",
+        "textExcerptLimitChars",
+        "markdownLimitChars",
+        "bodyBytes",
+        "bodyTruncated",
+        "textTruncated",
+        "charset",
+        "charsetSource"
+      ],
+      "type": "object"
+    },
+    "error": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "code": {
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "code",
+            "message"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "fetchedAt": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "finalUrl": {
+      "type": "string"
+    },
+    "markdown": {
+      "type": "string"
+    },
+    "ok": {
+      "const": true,
+      "type": "boolean"
+    },
+    "requestedUrl": {
+      "type": "string"
+    },
+    "sourceOk": {
+      "type": "boolean"
+    },
+    "status": {
+      "type": "integer"
+    },
+    "title": {
+      "type": "string"
+    },
+    "truncated": {
+      "type": "boolean"
+    },
+    "url": {
+      "type": "string"
+    },
+    "wordCount": {
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "ok",
+    "requestedUrl",
+    "finalUrl",
+    "url",
+    "status",
+    "sourceOk",
+    "error",
+    "title",
+    "markdown",
+    "wordCount",
+    "truncated",
+    "capture",
+    "fetchedAt"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 9, 2026

changedInput schema / properties / url / description

Previous value: -"Public http(s) URL to read as Markdown"New value: +"Public HTTP(S) URL whose readable body is needed as Markdown. Content is fetched without JavaScript rendering and may be truncated at 40,000 characters."

First observedJun 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are present, so the description carries the full burden, and it does well: it discloses that Markdown is capped at 40,000 characters, no JavaScript is executed, and which DOM regions are stripped. It also surfaces the payment-challenge/credential binding and retry behavior. The last two sentences are confident but somewhat cryptic about the challenge flow, keeping it just short of a 5.

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?

Front-loads purpose and return format, then alternatives, then constraints. Mostly efficient, though the trailing payment-challenge/credential sentences are dense and their relevance to an ordinary read call is not obvious.

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?

An output schema exists, so return values need not be spelled out, and the description covers scope, alternatives, truncation, and JS behavior. The one gap is a clean explanation of the payment-challenge/credential flow, which is asserted rather than described.

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 description coverage is 100% for the single `url` parameter, and the schema already documents no-JS fetching, the 40,000-char truncation, and the status/sourceOk/error/truncated/capture review. The description adds no format or syntax detail beyond the schema, 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?

States a specific verb (fetch) and resource (public HTTP(S) page) and the exact return shape (readable body as cleaned Markdown for LLM context), including what is preserved and dropped. It explicitly differentiates itself from the sibling `extract` tool. An agent can distinguish it from siblings without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use `extract` instead when metadata, JSON-LD, Open Graph/Twitter tags, or a link inventory are needed. This is a clear when-to-use-this-vs-alternative rule, plus retry guidance for the payment/credential case.

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

All x402-data-gateway tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.