Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

clean_url

[$0.001] Fetch any public HTTPS webpage with SSRF protection, strip navigation/ad boilerplate, and return clean LLM-ready Markdown, word count, and extracted entities as JSON.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clean_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoAny public URL to fetch, clean, and extract content from
summarizeNoAdd LLM-powered summary with entity extraction and sentiment scoring
timeout_msNoOptional deadline in ms. If the local LLM would exceed it, the response comes back fast with "degraded": true and non-LLM/cached data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it delivers: SSRF protection, boilerplate stripping, the exact return payload, and a $0.001 price are all disclosed. It stops short of stating failure modes, rate limits, or handling of non-HTML content, which keeps it below a 5.

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 sentence that front-loads the action and packs the security guarantee, processing behavior, and output shape with no filler. It is dense but readable; splitting the return-value clause would slightly improve scannability.

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

Completeness4/5

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

With no output schema, the description usefully spells out the return payload (Markdown, word count, entities, JSON), which an agent needs in order to call it confidently. The main remaining gap is error and edge-case behavior for non-fetchable URLs, which the parameters do not cover either.

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%, including the degraded-response behavior for timeout_ms, so the schema already carries parameter meaning. The description adds only the entity-extraction outcome and cost, not extra syntax or defaults, so the baseline of 3 applies.

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

Purpose4/5

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

The description uses a concrete verb chain (fetch, strip, return) against a specific resource (any public HTTPS webpage) and names the outputs (Markdown, word count, entities, JSON). It is unambiguous what the tool does, though it never states how it differs from adjacent tools like ai_summarize, which its own summarize parameter partially overlaps with.

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?

'Fetch any public HTTPS webpage' implicitly scopes usage to public, HTTPS-only URLs, which is a real constraint an agent can act on. However, there is no explicit when-to-use/when-not guidance and no routing to alternatives such as ai_summarize or search, leaving selection to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources