Skip to main content
Glama
AgentiLoop

pagewire

by AgentiLoop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Read a page + 4 linked pages ($0.03/call)

crawl_site
Read-only

Fetch a public page plus up to 4 linked same-host pages in one call, returning each as title and clean Markdown for reading docs or small sites.

Instructions

Fetch a public web page plus up to 4 pages on the same host that it links to (in link order, or only those whose path starts with prefix), and return each one as title + clean Markdown. Good for reading a docs section or a small site in one call. No model call, deterministic. For a single page use page_to_markdown (cheaper), for metadata only use page_metadata. Plain HTTP fetch (no JavaScript rendering, 15 s timeout, only the first 2 MB is read). Errors (non-public URL, upstream HTTP error, timeout, non-text content) return isError with the reason and are never charged. Price: $0.03 USDC per call via x402 (USDC on Base or Solana, no account; nothing is charged for a bad input). First $0.1 of calls per day per client are free (no payment needed).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic http(s) page to fetch
limitNoLinked pages to read (default 4)
prefixNoOnly follow links whose path starts with this, e.g. /docs/
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value (x402 v2 payment payload signed for one entry of the `accepts` list returned when this tool is called without it). Omit to get the price and payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial extra behavior: no JavaScript rendering, 15 s timeout, 2 MB read cap, link-order vs prefix filtering, and that errors (non-public URL, HTTP error, timeout, non-text) return isError and are never charged. Pricing, payment channel, and a free daily tier are also disclosed.

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?

Purpose and scope are front-loaded in the first sentence, then alternatives, then behavioral limits, then cost. Four tight sentences with no filler; every clause carries information an agent needs before calling a paid tool.

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?

No output schema exists, yet the description specifies the return format (title + clean Markdown per page) and the error contract. Combined with the exact cost and payment mechanics, an agent has everything needed to call this correctly.

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, but the description adds real meaning: it clarifies that the 4-page cap is 'up to 4', that links are followed 'in link order', and that prefix restricts by path ('/docs/'). The payment parameter is left entirely to the schema, which is acceptable given its detailed self-description.

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 (fetch) plus resource (a public page and up to 4 same-host links) and the return shape (title + clean Markdown). It explicitly contrasts itself with page_to_markdown and page_metadata, so an agent can distinguish it from siblings without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives positive guidance ('good for reading a docs section or a small site in one call') and names both alternatives with the condition that selects them: single page -> page_to_markdown (cheaper), metadata only -> page_metadata. Nothing left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools