Skip to main content
Glama

Base Agent Due-Diligence Kit

Web Reader ($0.005)

web_read
Read-onlyIdempotent

Fetch any public web page and return clean Markdown plus metadata (title, description, author, date, language, canonical). Main-content extraction, absolute links, optional link list. Respects robots.txt. Failed fetches are not settled. Limits: only the first 160 KB of the page is parsed and at most 40000 characters are returned; inputTruncated/truncated tell you when that happened. PAID: $0.005 per call in USDC on Base via x402, or use a 0.25 USDC transfer pass (pay_tx). See payment_options. By Bolt.

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_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoMax Markdown characters to return (1000-40000, default 20000)
urlYesPublic http(s) URL to read
linksNoSet 1 to also return the list of links found in the content
pay_txNoOptional, for the plain-transfer option (no x402 needed): hash of a USDC transfer of >= 0.25 USDC to this server's receiving address (get it from the payment_options tool). One transfer unlocks every paid tool for 24h.
pay_chainNoChain of pay_tx (default: inferred; 0x hash = base, base58 signature = solana)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent, but the description adds substantial behavior beyond them: main-content extraction, absolutized links, optional link list, robots.txt compliance, billing semantics for failures, and hard limits (160 KB parsed, 40000 chars returned) with inputTruncated/truncated signals. That is exactly the kind of operationally load-bearing detail annotations cannot express.

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?

Information is front-loaded: purpose and output first, then limits, then payment, then attribution. Some telegraphic fragments ('Main-content extraction, absolute links, optional link list.') and the trailing 'By Bolt.' are low-value, but nearly every clause carries operational meaning.

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 paid, open-world fetch tool with no output schema, the description covers inputs, return payload, truncation signals, billing risk on failure, robots.txt, and the two payment paths. An agent has everything needed to call it and interpret the cost and truncation outcomes.

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 the baseline is 3, and the description goes further by naming pay_tx ('use a 0.25 USDC transfer pass (pay_tx)'), describing the optional link list that maps to links, and restating the 40000-char ceiling for max. pay_chain is left entirely to the schema, which prevents a higher score.

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 ('Fetch any public web page') and names the exact return shape (clean Markdown plus title/description/author/date/language/canonical metadata). It is unmistakably distinct from every sibling, which are all crypto/contract/payment analysis tools, so an agent can select it 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?

Gives clear operating context: public http(s) pages only, robots.txt respected, failed fetches not billed, and it routes the payment decision explicitly to payment_options / x402 or pay_tx. It lacks an explicit 'when not to use this' or a comparison to an alternative fetching path, which keeps it short of a 5.

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