Skip to main content
Glama
AgentiLoop

pagewire

by AgentiLoop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Web page → Markdown ($0.01/call)

page_to_markdown
Read-only

Fetch a public web page through pagewire and convert it into clean Markdown, with title, description, and links, stripping scripts, styles, and navigation.

Instructions

Fetch a public web page and return its title, description, clean Markdown (scripts, styles, nav chrome removed) and the list of links. No model call, deterministic. Use it to read the content of one page; use page_metadata if you only need title/OpenGraph/JSON-LD (cheaper), or crawl_site to read the page plus the pages it links to in one call. 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.01 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
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.6/5.0
Behavior5/5

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

Annotations only cover readOnlyHint/openWorldHint, but the description adds substantial behavior: no JS rendering, plain HTTP fetch, 15 s timeout, 2 MB read cap, deterministic no-model-call, and error semantics (isError with reason, never charged). Payment/free-tier mechanics 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.

Conciseness4/5

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

Dense but front-loaded: purpose first, then routing guidance, then constraints and pricing. Every clause carries useful information, though the pricing/free-tier tail is comparatively verbose.

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?

Despite no output schema, the description enumerates the return payload (title, description, Markdown, links) and covers failure modes and cost, so an agent has everything needed to call and interpret results correctly.

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 description coverage is 100%, so both parameters (url, payment) are already documented, including the 'omit to get price' behavior. The description's payment details largely mirror the schema rather than adding new parameter meaning, so the baseline of 3 applies.

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 a public web page and return its title, description, clean Markdown and the list of links') and explicitly distinguishes itself from both siblings, page_metadata and crawl_site. An agent can pick it apart from siblings without opening any schema.

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 explicit when-to-use ('read the content of one page') plus named alternatives and the conditions that select them: page_metadata when only metadata is needed (noted as cheaper), crawl_site for page-plus-linked-pages. No inference required.

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