Mart402 Documents & Web

Extract Url

extract_url

Idempotent

Extract a web page to clean Markdown + metadata (auto JS rendering, robots.txt respected). $0.005 fast / $0.01 rendered; cached results half price. Choose this when you need a web PAGE as clean Markdown to read yourself; to fill a schema use structured_extract, for a PDF use pdf_info then parse_document.

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

Input Schema

Name	Required	Description	Default
`ttl`	No	cache seconds (0 = no cache)
`url`	Yes	Absolute http(s) URL of the input (web page or PDF, per tool)
`mode`	No	Extraction mode: auto (fast with rendered fallback), fast, heavy	auto
`x_payment`	No	Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged.

Output Schema

Name	Required	Description
`body`	Yes	JSON body of the underlying call (see /samples/{product} for each product's shape)
`status`	Yes	HTTP status of the underlying call (200 result, 402 payment terms, 4xx input error)
`how_to_pay`	No
`receipt_id`	No	set on paid results; free re-fetch via get_receipt
`payment_required`	No	true when status is 402: body holds x402 payment terms, not a result. Pay and call again with x_payment

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare openWorldHint=true, idempotentHint=true, destructiveHint=false, so the burden is partly lifted. The description adds genuinely non-structured behavior: automatic JS rendering, robots.txt compliance, and tiered pricing with a cache discount. It does not explain the x402 payment handshake beyond what the schema says, so not a full 5.

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?

Three compact sentences, zero filler: purpose first, cost/behavior second, routing last. Every clause carries information an agent uses for selection or invocation.

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?

Output schema exists, so return values need not be described. Given the tool's complexity (payment, modes, caching), the description covers purpose, cost, behavioral traits, and sibling routing, leaving nothing critical to inference.

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%, so baseline is 3, but the description adds economic meaning to mode selection ('$0.005 fast / $0.01 rendered; cached results half price') and ties caching to cost, which the schema's ttl description does not. Minor friction: it says 'rendered' while the enum value is 'heavy', leaving the mapping implicit.

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 ('Extract a web page to clean Markdown + metadata') with the output artifact named. It explicitly carves itself out from structured_extract (schema filling) and pdf_info/parse_document (PDFs), so an agent can route without opening sibling schemas.

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

Usage Guidelines5/5

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

Explicit selection rules: 'Choose this when you need a web PAGE as clean Markdown to read yourself', with named alternatives for the two nearest competing intents. Both the use case and the when-not conditions are stated.

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

All Mart402 Documents & Web tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?