Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PAGEWIRE_MCP_URLNoThe URL of the PageWire MCP server.https://pagewire.dev/mcp
PAGEWIRE_MCP_TIMEOUT_MSNoThe timeout in milliseconds for the PageWire MCP server.60000

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
page_to_markdownA

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).

page_metadataA

Fetch a public web page and return its metadata: title, description, canonical URL, language, OpenGraph and Twitter card tags, icons and parsed JSON-LD blocks. Use it for link previews, SEO checks or structured data (JSON-LD) without the page body; use page_to_markdown when you need the readable text and links. 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.005 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).

crawl_siteA

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).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct output: clean Markdown body, metadata/JSON-LD only, or a multi-page crawl. The descriptions explicitly cross-reference each other ("use page_metadata if you only need title...", "use crawl_site to read the page plus the pages it links to"), leaving no real ambiguity about selection.

Naming Consistency4/5

All names are snake_case with a consistent noun/verb structure (page_to_markdown, page_metadata, crawl_site), and the two 'page' tools share a clear prefix. The 'crawl_' verb on the third tool is a minor deviation from the 'page_' prefix pattern but remains readable and descriptive.

Tool Count5/5

Three tools is well scoped for a page-fetching service, and each one earns its place by covering a genuinely different retrieval mode (full body, metadata only, small crawl). No redundant or filler tools.

Completeness4/5

The surface covers the core fetch lifecycle: single-page content, lightweight metadata, and same-host multi-page crawling, with clear error and pricing semantics. Minor gaps remain around cross-host or larger batch fetching and deeper crawl controls (e.g. page limits, sitemap), but agents can work around these with repeated calls.

Maintenance

ActivityMaintained
ResponsivenessNo issues