Turn any public web page, including JavaScript-heavy ones, into clean readable markdown (or text/html) with title and byline. Rendered by a real browser then stripped to the main content. Ideal for feeding pages to LLMs. JSON response. [Paid: $0.006 USDC per call via x402 on Base; the calling client pays automatically.]
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public page URL | |
| format | No | Output format, default markdown |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description provides important behavioral details: uses a real browser, strips to main content, outputs JSON, and mentions a payment mechanism ($0.006 USDC via x402). This adds substantial value beyond the schema.
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?
The description is concise, front-loaded with the main action, and every sentence adds value. No unnecessary words or repetition.
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?
Given no output schema, the description explains the return format (clean markdown/text/html with title and byline, JSON response) and covers payment. It lacks error handling details but is reasonably complete for a simple tool.
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 parameters ('url', 'format') are well-described in the schema. The description only implicitly mentions formats ('markdown, text/html'), adding no new meaning beyond what the schema provides.
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 starts with a specific verb 'Turn any public web page' and specifies the resource (web pages) and output (clean readable markdown with title and byline). It clearly distinguishes from siblings like screenshot or pdf-extract by focusing on text extraction.
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 states 'Ideal for feeding pages to LLMs', implying a use case, but does not explicitly mention when not to use it or provide alternatives among sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each of the 30 tools has a highly specific, non-overlapping purpose, from brand visibility to chemical safety to YouTube transcripts. Descriptions are detailed and clearly differentiate each tool's function, eliminating ambiguity.
All tool names use lowercase with hyphens, creating a consistent visual pattern. However, the structure varies: some are noun-verb (email-validate, pdf-extract), others noun-noun (brand-visibility, chem-compat). This minor inconsistency prevents a perfect score.
With 30 tools, the server offers a very broad surface. While each tool earns its place as a distinct utility, the high count may overwhelm agents and dilute focus. It is borderline heavy for a single server, hence a score of 3.
The tool set covers a wide range of domains: business, chemicals, crypto, domain, email, finance, holidays, trade, jobs, legal, mapping, medical, news, packages, electronics, PDF, product, recall, sanctions, screenshots, SEC, tech stack, web archive, web search, YouTube. Yet it lacks some common utilities like weather, translation, or image analysis, leaving notable gaps for a general-purpose utility server.