Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
page_to_markdownA

Fetch a web page URL and convert it to clean Markdown optimized for LLM context. Preserves headings, code blocks (with language hints), links, and tables; keeps the main content and drops navigation, headers, footers, and sidebars. It fetches without cookies and runs no page scripts, so a page behind a sign-in or one rendered only by JavaScript comes back as its login page or with no content. For those, pass the page HTML you already have from a browser tool as html (with its url, relative links resolve and nothing is fetched), or ask the user to turn on Agent Bridge in the Page2AI browser extension 1.6.0 or later (if its popup has no Agent Bridge switch, that install is an older store version and the extension must be updated first): while it is connected, url pages open in the user's own browser with its cookies and scripts, and a page the extension declines is fetched by the server, with a note saying why. It requests only the URL given, as a browser opens a page, so docs sites return the page itself, not a Markdown copy of it; a URL that names a Markdown or text file (a raw GitHub README.md, an llms.txt) comes back as written. A long page comes back in parts (max_length, start_index), the first part listing the page's sections, and a page the server cannot read comes back with the next step to take. Discovers tab groups statically and emits each panel as a ### Tab: {label} section instead of concatenating (prevents Python+TypeScript examples merging into one broken block). Zero external API calls: pages are parsed locally (linkedom) or in the user's browser.

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 1 tool

Disambiguation5/5

With a single tool there is no possibility of misselection; the tool's purpose (fetch a URL or supplied HTML and return clean Markdown) is unambiguous and self-contained. No sibling tools overlap with it.

Naming Consistency5/5

A single snake_case verb_noun name (page_to_markdown) that precisely describes the action and target. There is no mixed convention to detract from it.

Tool Count3/5

The tool is genuinely multi-purpose (URL fetch, raw HTML passthrough, browser bridge fallback, paginated output) so one tool is defensible, but a single-tool surface is thin and users may expect at least a batch or metadata companion. Borderline rather than clearly well-scoped.

Completeness4/5

For a page-to-Markdown domain it covers the main paths: direct fetch, HTML you already have, browser-authenticated fetch, long-page pagination, and error guidance. Minor gaps exist (e.g. no explicit batch/multi-URL conversion), but agents can work around them by calling repeatedly.

Maintenance

ActivityActive
ResponsivenessUnresponsive