Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Page to clean text ($0.003)

scrape_text
Read-only

PAID $0.003 USDC. Any web page as clean, LLM-ready Markdown text with navigation, ads and boilerplate stripped: title, text and character count. Example: url=https://example.com. No charge if the page cannot be fetched.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL
api_keyNoOptional prepaid key (sk_scrapling_...) or catalog pass token (sdp_..., from pass_day/pass_month). Otherwise pay per call with x402 via _meta['x402/payment'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Optional prepaid key (sk_scrapling_...). Otherwise pay per call with x402 via _meta['x402/payment']."New value: +"Optional prepaid key (sk_scrapling_...) or catalog pass token (sdp_..., from pass_day/pass_month). Otherwise pay per call with x402 via _meta['x402/payment']."
  2. Added

TDQS

C2.9/5.0
Behavior2/5

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

The billing model ($0.003 USDC, no charge on fetch failure) is genuinely useful context not present in annotations. However, the description's 'Any web page' scope openly contradicts the openWorldHint=false annotation, which declares the tool does not reach into an open world of external entities; failure modes such as timeouts, JS-rendered pages, or size limits are also unstated.

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-loaded with cost and output shape, then the example, then the failure/refund clause — information-dense with no filler. It is packed tightly into a couple of sentences but each clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output contents, cost, and refund behavior are covered, which is reasonable for a 2-parameter read-only tool with no output schema. What is missing for correct selection is the relationship to scrape_url and any statement about page-type limitations or payment precedence between api_key and x402.

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 url and the optional api_key/payment path are already documented in the schema. The description only adds a literal example URL, giving no extra detail on payment precedence or what happens when api_key and x402 are both supplied.

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?

Names a specific transformation (web page → clean, LLM-ready Markdown) and enumerates the returned fields (title, text, character count), so the agent knows exactly what it gets. It never mentions the obvious sibling scrape_url, so the agent cannot tell from this text which scraper to pick.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus scrape_url or any other sibling, no prerequisites, and no conditions under which the call should be avoided. The only guidance is a URL example and a refund note, which is invocation syntax rather than usage selection.

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

All Scrapling x402 Data Store 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