Convert one public webpage to Markdown for AI agents. $0.01 per successful scrape, paid in USDC on Base via x402.
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another operation. Its purpose (convert a single public webpage to Markdown) is unambiguous.
The lone tool uses a clean snake_case verb_noun pattern (scrape_webpage) that would extend predictably to a larger set. With one tool there is no risk of mixed conventions.
A single tool is thin even for a narrowly scoped scraping service; common companion operations (batch scrape, raw HTML fetch, payment/balance check) are absent. The one tool does earn its place, so this is borderline rather than a mismatch.
Core single-page conversion is covered, but for a paid x402 service there is no way to check balance, usage history, or payment status, and no batch/crawl or output-format options. Agents can still accomplish the primary task but will hit dead ends around payment and scale.
Convert one public webpage to Markdown. Costs $0.01 per successful scrape, paid in USDC on Base through x402.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public HTTP or HTTPS webpage URL to convert. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and it does add genuinely useful behavior: a $0.01 fee charged only on success, paid in USDC on Base via x402. That is real billing and cost semantics an agent must know before calling. It still omits failure behavior, rate limits, timeouts/JS rendering, and whether any credentials are needed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with zero filler: what it does first, then the cost/payment terms. Nothing is buried and nothing is redundant.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter tool with no output schema, the description covers the essential unknowns: output format (Markdown) and payment mechanics. It is nearly complete, missing only failure/retry behavior and rendering characteristics that an agent might want before spending money.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents the single URL parameter at 100% coverage, including the HTTP/HTTPS format restriction. The description adds only the 'public' qualifier, implying unauthenticated, openly reachable pages, which is marginal beyond the schema baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a precise verb and resource ('Convert one public webpage to Markdown'), so the transformation and its input type are unambiguous. There are no siblings to distinguish from, but the scope word 'one' correctly signals single-URL semantics.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context by limiting inputs to 'public' webpages and disclosing a per-scrape fee, which tells the agent this is a paid, unauthenticated-page tool. However, it never states when to use this tool versus other retrieval approaches or what to do when a page isn't public, leaving conditions to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
scrape_webpage
Add one secure layer between your agents and this server.