Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

url-to-text

[x402 paid: $0.002 USDC on Base] Any http(s) page as clean plain text in one call - ready for LLM context. No key, no scraping setup. tools/call returns the live payment challenge.

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": "url-to-text"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoexample: https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With zero annotations the description carries the full burden, and it does disclose the two things an agent most needs: no API key is required, and the call is x402-metered at $0.002 USDC on Base with tools/call returning the live payment challenge. It omits rate limits, page-size/timeout limits, and failure behavior, so it is strong but not complete.

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?

Two compact sentences with no filler, and the payment/access terms are up front. The bracketed cost tag slightly delays the purpose statement, but the information is genuinely load-bearing rather than noise.

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?

For a one-parameter fetch-and-convert tool with full schema coverage, the description covers purpose, access, and pricing. Since no output schema exists, "clean plain text" adequately characterizes the return, and nothing critical to invoking it is missing.

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?

The schema already documents the single url parameter at 100% coverage, including an example value. The description only implies http(s) scheme acceptance, adding nothing about normalization, redirects, or why url is not marked required. Baseline 3 applies when the schema does the work.

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?

"Any http(s) page as clean plain text in one call" states a specific transformation and output format, plus the intended consumer ("ready for LLM context"). It never contrasts itself with the closest sibling, tool_ai_url-research, so an agent must infer that one fetches/renders while the other researches.

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 "ready for LLM context" and "no key, no scraping setup," which suggests fetching raw page text when you have a URL. There is no explicit when-to-use vs. when-not, no guidance on non-HTML or JS-heavy pages, and no named alternative.

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