Skip to main content
Glama

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

tool_web_read

[x402 paid: $0.002 USDC on Base] Read any web page as clean plain text (up to 8k chars) — ready to paste into an LLM context. 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": "tool_web_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoexample: https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose important behavior: a $0.002 USDC Base fee, the x402 challenge returned by the first tools/call, and an 8k character output cap. However, it leaves open whether content beyond 8k is truncated or paginated, whether JavaScript-rendered pages work, and what failures look like after payment — meaningful gaps for a paid read tool.

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 tight sentences with zero filler, and the size cap and output format are stated inline. The bracketed pricing tag leads the text, which slightly delays the core purpose statement, but nothing is wasted.

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

Completeness2/5

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

For a paid tool with no annotations and no output schema, the description should explain the payment retry flow more concretely (does the agent need to call twice?) and how the 8k limit is applied. As written, an agent could attempt a call, receive a 402-style challenge, and not know the expected follow-up, which is a significant completeness gap.

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?

Only one parameter (url) with 100% schema description coverage including an example, so the schema already does the work; there is essentially no room for the description to add meaning. Baseline for a single fully-documented parameter.

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?

States a specific verb and resource — "Read any web page as clean plain text (up to 8k chars)" — plus the downstream use case (paste into an LLM context). It does not distinguish itself from plausible siblings like tool_ai_url-research or tool_ai_summarize, so it falls short of a 5.

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 to paste into an LLM context," telling the agent the output is meant for LLM consumption rather than analysis. There is no explicit when-to-use versus when-to-pick-a-sibling guidance, and no statement of exclusions (e.g. JS-heavy pages).

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