agentdata-nl

web_contents

Read any web page as clean LLM-ready markdown for $0.0015 — the cheapest x402 page reader, and the natural companion to /web/search. Send a URL, get back the readable core: title, headings, paragraphs, lists and links, stripped of scripts, styles, navigation and other boilerplate. Choose markdown or plain text and cap the size with max_chars (default 20000; a truncated flag tells you when the cut hit). Unreachable or non-HTML targets cost nothing. Pay per call in USDC, no account, no API key.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	The http(s) URL of the page to read. Literal IP addresses, localhost and non-http(s) schemes are rejected.
`format`	No	markdown (default) keeps #-headings, [text](url) links and - lists; text is flat plain text	markdown
`max_chars`	No	Maximum content length in characters (1000-100000, default 20000); longer pages are cut and flagged truncated

TDQS

A4.6/5.0

Behavior5/5

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

Despite no annotations, the description fully discloses behavior: stripping scripts/styles/navigation, output format options, max_chars with truncated flag, handling of unreachable or non-HTML URLs, and payment in USDC without account needed.

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 description is a focused paragraph that front-loads the core purpose. Each sentence adds distinct information, though it could be slightly more concise without losing clarity.

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?

Given the tool's simplicity and no output schema, the description is complete: it explains the readable core (title, headings, etc.), output formats, size cap, and cost structure, fully covering what an agent needs to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. Description adds value by explaining how formats differ, specifying default max_chars (20000) and the truncated flag, and clarifying URL restrictions (no IP addresses, localhost, non-http schemes).

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

Purpose5/5

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

The description clearly states the tool reads web pages and returns clean markdown or plain text. It distinguishes itself from sibling tools like web_search and web_crawl by emphasizing it is the 'natural companion to /web/search' and the cheapest x402 page reader.

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

Usage Guidelines4/5

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

Provides clear context: send a URL, choose format, cap size, and notes cost ($0.0015) and that unreachable targets cost nothing. Does not explicitly exclude alternatives, but the use case is well-defined.

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

All agentdata-nl tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Every tool targets a distinct action and domain: country-specific company checks (check_ch_company, check_fr_company, etc.), insolvency checks, crypto signals, x402 network tools, etc. Descriptions are detailed and make boundaries clear, with no two tools appearing to do the same thing.

Naming Consistency5/5

Tool names follow very consistent patterns: 'check_<country>_<entity>' for registers, 'crypto_*' for crypto intelligence, 'x402_*' for x402 network functions, 'screen_*' for screening, and a few free-form names like 'verify_eu_vat' and 'lookup_lei' that still fit the verb_noun style. No mixing of conventions.

Tool Count4/5

39 tools is high but justified by the broad scope: the server aggregates many country-specific checks, insolvency registers, crypto tools, x402 monitoring, and auxiliary functions (like phone number buying, LEI lookup). Each tool serves a clear purpose, and the count is not excessive given the coverage. A slight reduction could be possible by merging some country checks, but overall it's reasonable.

Completeness4/5

The server covers major European company registers (CH, UK, FR, NL, NO, PL, CZ, FI), insolvency checks (NL, FR), sanctions screening, VAT validation, crypto market intelligence, and x402 network tools. It acknowledges gaps (e.g., no German check) and provides fallback tools like 'screen_eu_supplier' and 'file_agent_want'. Minor missing pieces (e.g., Italian company check) keep it from a perfect 5.

Resources

Need Help?