Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

verifystack_clean_url

Fetches any public URL and strips ads, scripts, and navigation boilerplate to return clean LLM-ready Markdown with metadata and token-count estimates.

Instructions

Paid x402 API ($0.005 USDC on Base): Fetches any public URL, strips ads/scripts/navigation boilerplate, and returns clean LLM-ready Markdown, metadata, and token-count estimation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "verifystack_clean_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http:// or https:// URL to fetch and clean
maxCharsNoMaximum output length in characters (200-40000, default 12000)
includeLinksNoInclude extracted page links array (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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 disclose the most important behavioral fact: this is a paid x402 endpoint at $0.005 USDC on Base, which implies payment setup and per-call cost. It also describes the return payload shape, but omits failure semantics (is payment charged on error?), timeouts, rate limits, and dynamic-content handling, leaving meaningful gaps for an unannotated tool.

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?

A single dense sentence that front-loads the payment model before the functional description, which is the right ordering for a paid call. Slightly overloaded by the parenthetical price clause, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only three well-documented parameters the schema burden is low, and the description usefully compensates for the absent output schema by naming the returned Markdown, metadata, and token counts. It is still short of complete for a paid, unannotated tool: cost-charging semantics on failure and output structure details remain unstated.

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

Parameters3/5

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

Schema description coverage is 100%, so url, maxChars, and includeLinks are already fully documented in the input schema. The description adds no parameter-level meaning (e.g., how maxChars interacts with token estimation), so the baseline 3 applies.

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?

States a specific verb and resource ("Fetches any public URL"), then names exactly what it produces (clean LLM-ready Markdown, metadata, token-count estimation) and what it removes (ads/scripts/navigation boilerplate). This is clearly distinct from the sibling crypto tools (arbitrage, liquidation, signature verification), so an agent can route to it without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied by the wording "any public URL" and "LLM-ready Markdown," which suggests use when page content needs to be read by a model. However, there is no explicit when-to-use/when-not-to-use statement, no mention of alternatives, and no guidance for edge cases like paywalled, JS-rendered, or non-HTML resources.

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