Skip to main content
Glama
Sign In

Lordevo Shop (x402 website checks)

by com.lordevo
OverviewDiscussionsAdmin

Batch URL to Markdown: up to 5 web pages per call (LLM-ready) ($0.01/call)

page_markdown_batch
Read-onlyIdempotent

$0.01 per call (x402, USDC on Base; not covered by the free trial). [Fetch and read the web] Batch URL to Markdown web scraper for RAG ingest and research agents. page-markdown for 1-5 public URLs in one paid call (comma-separated): the same clean main-content Markdown, metadata and options (include_links, max_tokens) per URL, with a per-URL error (robots_disallowed, target_http_error...) where a page cannot be read. If every URL fails, nothing is charged. One payment for 5 URLs = $0.002 per URL, the same as 5 single page-markdown calls; for 1-4 URLs single calls ($0.002 each) are cheaper. robots.txt checked per URL and redirect. ~2-10 s.

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": {
      "urls": "<urls>"
    },
    "name": "page_markdown_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes1-5 public http(s) URLs, comma-separated
max_tokensNoCut the Markdown to about this many tokens at block boundaries (100-100000); sets truncated and truncated_reason "max_tokens"
include_linksNofalse = drop link targets and images, keep the text (default true)true

Output Schema

NameRequiredDescriptionDefault
okNo
toolNo
cacheNo
countNo
_trialNoPresent when the call was a free trial call.
failedNo
resultsNo
providerNo
price_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "required": [
+        "tool",
+        "count",
+        "ok",
+        "results"
+      ]
+    },
+    {
+      "properties": {
+        "accepts": {
+          "type": "array"
+        },
+        "error": {
+          "type": "string"
+        },
+        "resource": {
+          "type": "object"
+        },
+        "x402Version": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "x402Version",
+        "accepts"
+      ]
+    },
+    {
+      "properties": {
+        "charged": {
+          "type": "boolean"
+        },
+        "error": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "_trial": {
+      "description": "Present when the call was a free trial call.",
+      "type": "object"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "count": {
+      "type": "integer"
+    },
+    "failed": {
+      "type": "integer"
+    },
+    "ok": {
+      "type": "integer"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "error": {
+            "type": "string"
+          },
+          "final_url": {
+            "type": "string"
+          },
+          "markdown": {
+            "type": "string"
+          },
+          "ok": {
+            "type": "boolean"
+          },
+          "truncated": {
+            "type": "boolean"
+          },
+          "truncated_reason": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "url",
+          "ok"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, and the description adds substantial context beyond them: pay-per-call x402/USDC billing outside the free trial, per-URL partial failure with error codes (robots_disallowed, target_http_error), robots.txt honored per URL and redirect, no charge if all URLs fail, and ~2-10 s latency. That is exactly the billing, failure-mode and timing information an agent needs before spending money.

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?

Pricing and identity are front-loaded and the cost-comparison sentence earns its place by driving a routing decision. Minor waste: the bracketed "[Fetch and read the web]" tag and a pricing figure largely duplicated from the title, plus a dense run of clauses in one sentence.

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 paid batch scraper with an output schema, the description covers cost model, batching trade-off, per-URL failure semantics, robots compliance and latency, so nothing an agent needs to call it safely is missing. Return structure is left to the output schema, which is appropriate.

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%, so urls, max_tokens and include_links are already fully documented including the truncation flag behavior. The description only restates the option names and the comma-separated URL format, adding no syntax or constraint meaning 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?

"Batch URL to Markdown web scraper for RAG ingest and research agents" gives a specific verb and resource, and it explicitly positions itself against the page_markdown sibling ("page-markdown for 1-5 public URLs in one paid call"). An agent can distinguish batch vs single-page scraping without opening either 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?

It states exactly when to use this tool and when not to: 5 URLs in one paid call is the same per-URL price as five singles, but "for 1-4 URLs single calls ($0.002 each) are cheaper." That is an explicit, actionable routing rule with a named alternative.

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

All Lordevo Shop (x402 website checks) toolsInspect
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