Fetch URL and return simplified markdown/text. Params: { url } (x402: 0.001 USDC per call)
HTTP equivalent: GET /x402/web-markdown Payment: x402 protocol — send X-PAYMENT header with base64 payment payload, or X-API-Key / X-Owner-Key / Bearer token to bypass.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no safety annotations beyond a title, the description appropriately discloses the x402 payment requirement and authentication options (X-PAYMENT header or key/token bypass). It also mentions the HTTP equivalent, adding useful context. However, it does not disclose potential errors, rate limits, or content size limitations.
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 exceptionally concise, with the core purpose in the first sentence and payment/auth details clearly separated. Every sentence adds necessary information without fluff, and the structure is easy to scan.
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 the tool's simplicity, the description covers the essential aspects: purpose, parameter name, and payment/auth details. It explains the return format (markdown/text), which is sufficient. However, it omits explicit instruction on whether the url parameter is mandatory and how errors are handled, which an agent would benefit from knowing.
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 input schema is empty, so the description's mention of the 'url' parameter adds the only parameter information available. However, it does not specify whether the parameter is required, its expected format, or any constraints, leaving ambiguity. Since the schema provides no coverage, the description partially compensates but lacks depth.
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 clearly states the tool fetches a URL and returns simplified markdown/text, using a specific verb and resource. This distinguishes it from siblings like web_fetch, which likely returns raw HTML or different formats.
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?
No guidance is provided on when to use this tool versus alternatives such as web_fetch or sitemap_reader. The description implies usage for fetching and converting URL content to markdown, but it does not state when not to use it or mention any alternative.
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.
Multiple tool pairs are exact duplicates (e.g., wallet_analysis/wallet_analyzer, honeypot_check/rugpull_detector, defi_yield/defi_yield_rates) with identical descriptions, and many overlapping scanners (squeeze_scanner variants). An agent cannot reliably distinguish these tools.
Names are all snake_case, but conventions vary wildly: some are resource names (btc_price), some are actions (list_magnets), some are generic utilities (calculator), and duplicates use different naming patterns for the same function (wallet_analysis vs wallet_analyzer). No consistent verb_noun or resource_action pattern.
139 tools is an extreme count for any MCP server, far exceeding the 50+ threshold. The scope is a grab-bag of unrelated domains (crypto, FDA, SEC, utilities, web scraping), suggesting no curation.
The set is a shallow pile of read-only queries and utilities with no lifecycle management for any one domain. Many sub-areas have only one or two tools, and duplicates occupy slots where distinct operations should be. The lack of a clear domain makes completeness impossible to assess, but the surface is redundant rather than comprehensive.