Skip to main content
Glama
Lumos-Labs-HQ

Amazon Q Web Documentation Reader

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
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
read_web_documentationA
Fetches and extracts clean documentation content from a web page.

This tool is designed to read documentation websites and extract the main
content in a clean, readable format suitable for analysis.

Args:
    url: The URL of the documentation page to read
    output_format: Output format - "markdown" (default) or "text"

Returns:
    Extracted documentation content with title and metadata
extract_code_examplesA
Extracts all code examples/blocks from a documentation page.

This tool specifically targets code blocks in documentation, useful for
finding implementation examples, snippets, and code samples.

Args:
    url: The URL of the documentation page

Returns:
    All code blocks found on the page with their detected languages
get_page_structureA
Extracts the heading structure and table of contents from a documentation page.

This tool helps understand the organization of a documentation page by
extracting all headings and their hierarchy.

Args:
    url: The URL of the documentation page

Returns:
    Hierarchical structure of headings on the page
get_documentation_linksA
Extracts all links from a documentation page, useful for discovering related docs.

This tool helps navigate documentation by finding all links on a page,
optionally filtering by a pattern.

Args:
    url: The URL of the documentation page
    filter_pattern: Optional pattern to filter links (e.g., "api", "guide")

Returns:
    List of links found on the page
read_multiple_docsA
Reads multiple documentation pages and combines their content.

This tool fetches and extracts content from multiple URLs, useful when
documentation is spread across several pages.

Args:
    urls: List of documentation URLs to read

Returns:
    Combined content from all pages

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct aspect of documentation: code blocks, links, page structure, single page content, and multiple pages. Descriptions clearly differentiate them, avoiding overlap.

Naming Consistency5/5

All tool names use snake_case with a clear verb_noun pattern (e.g., extract_code_examples, get_documentation_links), providing a predictable and consistent naming scheme.

Tool Count5/5

With 5 tools, the server is well-scoped: it covers all essential operations for documentation reading (single/multiple pages, code, links, structure) without unnecessary extras.

Completeness5/5

The tool set covers the core functionalities needed for a documentation reader: content extraction, structure, links, and code examples. Minor features like search are absent but not essential for the stated purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues