agentfuel402

fuel_clean_markdown

Fetch any public URL, strip ads, scripts, and noise, sanitize prompt injections, and return clean Markdown with token estimates for safe AI ingestion.

Instructions

Fetches any public URL, strips noise/scripts/ads, sanitizes prompt injections, and returns clean Markdown and token estimates. Cost: $0.005 USDC via x402.

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": "fuel_clean_markdown"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Public URL to fetch and clean
`strip_images`	No	Strip image markdown tags

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full load and does well: it discloses the cleaning pipeline (noise/scripts/ads removal), a security behavior (prompt-injection sanitization), the return payload (Markdown plus token estimates), and a concrete cost of $0.005 USDC via x402. What is missing is operational detail the agent would need at call time: whether payment is charged on failure, rate limits, size/timeout limits, and error shapes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, and the capability statement is front-loaded while the cost caveat is placed last where it is easiest to act on. Every clause adds distinct information (fetch, clean, sanitize, return format, price).

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?

For a two-parameter tool with no output schema, the definition covers purpose, transformation behavior, return type, and pricing — enough to call it correctly. The remaining gaps are failure semantics and payment mechanics (prepay vs. settle, what happens on a 402 response), which are relevant given the paid x402 model.

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 coverage is 100%, with both parameters documented in-schema, so the baseline is 3. The description adds no parameter-level meaning beyond the schema — notably it never mentions strip_images or how the sanitization/cleaning interacts with that flag.

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 gives a specific verb-and-resource pair ('Fetches any public URL ... returns clean Markdown') plus the transformation pipeline, so an agent knows exactly what comes back. It does not name or contrast any sibling tool, but the resource (arbitrary public web pages) is distinct enough from the other fuel_* tools that confusion is unlikely.

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?

'Fetches any public URL' implies the scope of applicability (public pages only), which is useful boundary information. However, there is no explicit when-to-use vs. when-not guidance, no mention of what happens with non-public or gated URLs, and no routing to an alternative for cases this tool does not cover.

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

Deploy Server