Skip to main content
Glama

Sitesy Website Intelligence

Read a web page

page_reader
Read-onlyIdempotent

Clean readable text and metadata from one web page, for summarising or quoting a page. Costs 0.01 USDC per call. The caller pays per call in USDC on Base through x402: the first call returns the payment requirements, and an x402 aware MCP client signs and retries automatically.

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

Input Schema

NameRequiredDescriptionDefault
urlYesA web page address, for example 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?

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely new behavior that annotations cannot express: a 0.01 USDC cost per call, the x402/Base payment rail, and the two-step flow where the first call returns payment requirements and the client signs and retries. It does not mention page-level limits (paywalls, JS-rendered pages, truncation).

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 sentences: capability first, then the cost/payment mechanics. Front-loaded and free of filler, though the payment sentence is dense and could be split for scanability.

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 single-URL read-only tool with a fully documented parameter and complete annotations, the description supplies what structured fields cannot: the cost and the x402 retry contract, which an agent must know to avoid treating the first-call payment response as an error. Return format need not be spelled out since no output schema exists but 'text and metadata' sets expectations.

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?

Only one parameter exists and its schema description coverage is 100%, including a format and example. The description adds no additional meaning about URL handling, so the baseline of 3 applies.

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 concrete action and resource: extracting 'clean readable text and metadata from one web page', plus the intended use ('summarising or quoting'). It is clear on its own, but it never distinguishes itself from the closely related siblings page_links or page_metadata, so an agent must infer the boundary from names alone.

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?

The phrase 'for summarising or quoting a page' implies a use context, and the payment note implicitly warns about cost per call. There is no explicit when-to-use/when-not-to-use guidance and no named alternative for link extraction or metadata-only lookups.

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