Lordevo Shop (x402 website checks)

Text chunker for RAG (heading-aware, token-sized chunks) ($0.002/call)

text_chunk

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Fetch and read the web] Splits text you send, or the main content of one public page, into heading-aware chunks of at most max_tokens with optional overlap, each with its heading path and an approximate token count, for RAG ingestion. Input: text (POST for long text) or url; max_tokens 50-4000, overlap_tokens. Limits: 400,000 characters, 2,000 chunks; robots.txt obeyed for url.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "text_chunk"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Public http(s) URL or bare domain, e.g. https://example.com (instead of text)
`text`	No	Plain text or Markdown, 1-400,000 characters (short text in the query; long text as POST JSON {"text": "..."}) (or give url)
`trial`	No	Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms.
`max_tokens`	No	Max tokens per chunk, 50-4000 (default 500)	500
`overlap_tokens`	No	Tokens repeated from the previous chunk, 0 to half of max_tokens (default 50)	50

Output Schema

Name	Required	Description
`tool`	No
`cache`	No
`_trial`	No	Present when the call was a free trial call.
`chunks`	No
`source`	No
`provider`	No
`price_usd`	No
`truncated`	No
`max_tokens`	No
`chunk_count`	No
`overlap_tokens`	No
`total_tokens_estimate`	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",
+        "chunk_count",
+        "chunks"
+      ]
+    },
+    {
+      "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"
+    },
+    "chunk_count": {
+      "type": "integer"
+    },
+    "chunks": {
+      "items": {
+        "properties": {
+          "approx_tokens": {
+            "type": "integer"
+          },
+          "heading": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "heading_path": {
+            "type": "array"
+          },
+          "index": {
+            "type": "integer"
+          },
+          "text": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "max_tokens": {
+      "type": "integer"
+    },
+    "overlap_tokens": {
+      "type": "integer"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "source": {
+      "enum": [
+        "text",
+        "url"
+      ],
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "total_tokens_estimate": {
+      "type": "integer"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

AddedNov 1, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's added value is the operational envelope: 400,000-character and 2,000-chunk caps, robots.txt compliance for url inputs, and the pricing/trial mechanics. That is genuine context not present in annotations or schema. It stops short of describing failure modes such as what happens when a page yields zero headings or the chunk cap is hit.

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?

The text is dense but well organized: pricing, then purpose and output shape, then inputs, then limits. Almost every clause carries information. The leading pricing parenthetical is somewhat noisy for an agent that is not making a purchase decision, and the trial mention is duplicated between title-adjacent text and the trial parameter.

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 explain return values, and annotations already carry the safety and idempotency profile. Combined with 100% schema coverage, the description closes the remaining gaps an agent needs: hard size/chunk limits, robots.txt behavior, payment and free-trial terms, and the two mutually exclusive input modes.

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 the baseline is 3. The description restates the max_tokens range and overlap behavior already documented in the schema, and its mention of 'text (POST for long text) or url' mirrors the schema's own mutual-exclusion notes. It adds no new syntax, format, or edge-case meaning beyond structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and output artifact: splits text or the main content of one public page into heading-aware chunks bounded by max_tokens with optional overlap, each carrying a heading path and approximate token count, for RAG ingestion. That is far more specific than a name restatement. It does not, however, explicitly distinguish itself from siblings like page_markdown, text_extract, or token_count, which overlap in the fetch-and-process space.

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 is implied by 'splits text you send, or the main content of one public page' and by the RAG-ingestion framing, and the free-trial path via try_free is mentioned. But there is no explicit when-to-use-this-vs-alternatives guidance; an agent choosing between this, page_markdown, and text_extract gets no routing rule.

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?