Skip to main content
Glama

read_url_text

Paid $0.02 (x402, USDC Base): fetch any http(s) web page and return clean plain text (title + visible body, scripts/styles stripped, up to 8000 chars). Gives text-only agents web reading. Private/internal hosts blocked.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL to read

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 well: it discloses a paid model ($0.02 via x402 in USDC on Base), the output shape, an 8000-char cap, and a host restriction. Gaps remain on failure modes, payment failure handling, and whether dynamic pages are rendered.

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?

A single dense sentence with no filler; the cost, the action, the return format, and the restriction all appear up front. Leading with the price is arguably better placed after the capability, but nothing is wasted.

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

Completeness4/5

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

There is no output schema, and the description compensates by describing the return value (title plus visible body, markup stripped, 8000-char ceiling) and the payment requirement. For a one-parameter read tool this is close to complete, with only error/render behavior left unspecified.

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% and the single 'url' parameter is already documented as an absolute http(s) URL, so the schema does the work. The description only reinforces this by saying 'any http(s) web page' and adds the private/internal host exclusion, which is modest added meaning.

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 http(s) web page') plus the exact transformation ('return clean plain text, title + visible body, scripts/styles stripped'). No sibling in the list does URL fetching, so the agent can route here unambiguously.

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 the scope statement and the note 'Gives text-only agents web reading', and the exclusion 'Private/internal hosts blocked' defines one boundary. There is, however, no explicit when-to-use or when-not framing relative to alternatives (e.g. research_report), and no guidance for JS-rendered or non-HTML 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