Lordevo Shop (x402 website checks)

PDF to text, page by page ($0.002/call)

pdf_text

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Fetch and read the web] Downloads one public PDF and returns its text layer page by page, with page count and title metadata. Input: url, optional max_pages. Limits: 10 MB, 50 pages, 500,000 characters; password-protected PDFs are refused and scanned images are not OCRed; robots.txt obeyed for every URL and redirect. Cached 1 h.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Public http(s) URL or bare domain, e.g. https://example.com
`trial`	No	Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms.
`max_pages`	No	Pages to read, 1-50 (default 50)	50

Output Schema

Name	Required	Description
`url`	No
`info`	No
`tool`	No
`bytes`	No
`cache`	No
`pages`	No
`_trial`	No	Present when the call was a free trial call.
`provider`	No
`price_usd`	No
`truncated`	No
`page_count`	No
`text_layer`	No
`pages_returned`	No
`total_characters`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / trial / description

Previous value: -"Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms."New value: +"Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms."

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / trial

Added value: +{
+  "description": "Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms.",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "required": [
+        "tool",
+        "url",
+        "page_count",
+        "pages"
+      ]
+    },
+    {
+      "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"
+    },
+    "bytes": {
+      "type": "integer"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "info": {
+      "type": "object"
+    },
+    "page_count": {
+      "type": "integer"
+    },
+    "pages": {
+      "items": {
+        "properties": {
+          "characters": {
+            "type": "integer"
+          },
+          "page": {
+            "type": "integer"
+          },
+          "text": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pages_returned": {
+      "type": "integer"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "text_layer": {
+      "type": "boolean"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "total_characters": {
+      "type": "integer"
+    },
+    "truncated": {
+      "type": "boolean"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedNov 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the bar is lower, yet the description still adds pricing ($0.002/call, USDC on Base), a 1-hour cache, and hard limits (10 MB, 50 pages, 500,000 chars). The main missing behavior is what happens on truncation — whether text is cut off or an error is raised at the character cap.

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 cost, then the bracketed category tag, then the core behavior, then limits and caching — a sensible order with essentially no filler. The markup-like pricing prefix and bracketed tag add mild visual noise but each carries decision-relevant information.

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?

With an output schema present, the description need not enumerate return fields, and it still summarizes them; annotations cover the safety profile and the schema documents all three parameters. Cost, limits, cache duration, refusal modes and the free-trial escape hatch are all present, leaving nothing an agent needs before calling.

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 100%, so the baseline is 3; the description goes beyond it by naming the operations-level caps (page count and 500,000-character ceiling) that constrain how max_pages should be set, and by explaining the trial fallback to try_free when the daily free quota is exhausted. It still does not clarify max_pages' string-with-pattern typing or its interaction with the character cap.

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 and resource — 'Downloads one public PDF and returns its text layer page by page, with page count and title metadata' — and the PDF-specific scope inherently separates it from HTML-oriented siblings like page_markdown and text_extract. An agent knows exactly what it gets back 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 real when-to-use boundaries: password-protected PDFs are refused, scanned images are not OCRed, and robots.txt is obeyed for every URL and redirect, which tells the agent when this tool will fail. It also routes cost-sensitive callers to the try_free sibling. It stops short of an explicit contrast such as 'for HTML pages use page_markdown instead.'

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) 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?