Skip to main content
Glama

read_page

Read one public web page as clean, LLM-ready markdown (title, main text, headings, lists, links, tables) with word count and a content hash. Paid per delivered page over x402; a blocked, missing, failing or refused page costs nothing.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
request_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 real work: it discloses the output shape, the billing model (x402, paid per delivered page), and the failure-charging policy — unusual and valuable behavioral context. Gaps remain on how payment is authorized, rate limits, and handling of JS-heavy or oversized pages.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly packed sentences with the capability first and the cost model second. Every clause carries information; nothing is redundant.

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?

With no output schema, the description does its job by describing the returned markdown components, word count, and content hash. The main shortfall is the unexplained request_id and the absence of any detail on how the x402 payment step is initiated, which matters for a metered tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain both parameters, and it explains neither. 'url' is inferable from 'read one public web page', but 'request_id' is entirely undocumented — for a per-page paid tool this is likely the idempotency/billing key, and its role is left completely to guesswork.

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?

The description names a specific verb and resource ('Read one public web page') and enumerates what comes back ('clean, LLM-ready markdown ... with word count and a content hash'). An agent knows exactly what this tool produces 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?

The scope constraints are clear: one page per call, public pages only, and billing applies only to delivered pages while blocked/missing/failing/refused pages are free. No alternatives are named, but there are no siblings to route between, so the guidance is sufficient for selection.

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.