Anti-bot web scraper returning token-optimized Markdown for AI agents ($0.002 USDC on Base).
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another. An agent can trivially determine when to invoke it.
The single name 'scrape' is a clean, lower-case verb and is internally consistent, but with only one tool there is no verb_noun pattern to evaluate. It is readable and predictable for its purpose.
A single tool is borderline thin for a scraping service; reasonable additions like crawl, batch-scrape, or output-format options are absent. The narrow single-operation scope makes one tool defensible but under-equipped.
The core scrape operation is covered, but there are no batch/multi-page/crawl variants and no visibility into options such as format, rendering mode, or timeout. Agents working around these limits face notable gaps.
Anti-bot web scraper returning token-optimized Markdown for AI agents ($0.002 USDC on Base)
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Target website URL |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It usefully discloses anti-bot handling, token-optimized Markdown output, and a pay-per-call cost on Base, but omits auth/payment mechanics, rate limits, failure modes, and what happens when anti-bot measures succeed or fail.
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?
A single tight sentence with no filler. Key details—anti-bot scraping, Markdown output, and cost—are front-loaded and the description is appropriately sized for a one-parameter tool.
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 simple one-parameter scraper with no output schema or annotations, the description conveys purpose, output format, anti-bot behavior, and cost. It stops short of explaining the payment flow and error handling, but covers enough for an agent to call it correctly.
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?
Schema coverage is 100%, so the single required url parameter is already fully documented in the schema. The description adds no syntax, format, or validation details beyond what the schema provides, making the baseline 3 appropriate.
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?
The description names a specific resource (a target website URL) and a specific output (token-optimized Markdown) while highlighting anti-bot capability. It is clear what the tool does, though the verb is implicit in 'scraper' rather than stated directly, and there are no siblings to distinguish from.
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?
There is no explicit guidance on when to use this tool, when not to use it, or what alternatives exist. The mention of anti-bot and cost implies suitable contexts but does not instruct the agent on selection or exclusions.
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
Add one secure layer between your agents and this server.