Skip to main content
Glama

YRUZ Web Extract (0.005 USDC)

web_extract
Read-onlyIdempotent

Fetch any public web page and return its main content as clean Markdown (navigation, scripts and boilerplate removed) with title, description, language, canonical URL, author, publish date, headings, links and images. Built for agents that need to read or cite the web. Follows up to 5 redirects; HTML, plain text and JSON pages. Price: 0.005 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"web_extract"}. Same tool over HTTP: https://yruz.one/api/extract?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FHTTP_402

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

Input Schema

NameRequiredDescriptionDefault
urlYespage URL (required), e.g. https://example.com/post
linksNo1 to include every link on the page (default 1)
max_charsNocap on the Markdown length, 1000-200000 (default 60000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / url / examples
      Added value: +[
      +  "https://en.wikipedia.org/wiki/HTTP_402"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: 5-redirect limit, supported content types (HTML/text/JSON), the x402 payment flow, that invalid input is refused before payment and failed runs are never charged, and that calls without payment return PaymentRequired. The annotations only cover safety/idempotency; this fills in cost and failure semantics.

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?

Front-loaded with the core capability in the first sentence; payment and invocation notes follow logically. Slightly padded by the repeated price mention (title and body) and the long percent-encoded HTTP example URL, but nothing is misleading.

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?

No output schema exists, so the description enumerates return fields itself, and it covers the paid-call error path that an agent will hit. Everything needed to call this successfully, including how to discover the exact call format, is present.

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%, so all three parameters (url, links, max_chars) are already documented with defaults and ranges. The description's mention of links and images in the output mildly relates to the 'links' flag but adds no new syntax or format detail. 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+resource (fetch a public web page, return main content as clean Markdown) and enumerates the returned fields (title, description, language, canonical URL, author, publish date, headings, links, images). An agent can distinguish this from link_preview or site_audit 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 Guidelines4/5

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

Names the intended use case ('built for agents that need to read or cite the web') and routes to get_example for invocation details, plus points at an equivalent HTTP endpoint. It does not explicitly contrast with sibling tools like link_preview, so no exclusions are stated.

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.