Skip to main content
Glama
mathisto

smart-webfetch-mcp

by mathisto

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

Tools

Functions exposed to the LLM to take actions

NameDescription
web_preflightA

Check page size and metadata before fetching. Returns estimated tokens, content type, and whether fetch is safe for context window. Always call this first to avoid context flooding.

web_smart_fetchA

Fetch URL with automatic truncation if content exceeds token limit. Use web_preflight first to check size. Returns markdown content.

web_fetch_codeA

Extract only code blocks from a page. Ideal for documentation pages with code examples. Returns code blocks with language annotations.

web_fetch_sectionA

Fetch only content under a specific heading. Case-insensitive heading match. Use when you only need a specific part of a large document.

web_fetch_chunkedA

Fetch large documents in chunks. Use for paginated reading of large docs. Returns chunk content plus metadata about total chunks available.

web_fetch_linksA

Extract all links from a page. Returns a markdown list of links with text and URL. Optionally filter by pattern or external links only.

web_fetch_tablesA

Extract tables from a page and return as markdown tables. Handles thead/tbody, th/td cells, colspan, and captions.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a specific aspect of web fetching (chunks, code, links, sections, tables, preflight checks, and general fetch) with no overlap in functionality.

Naming Consistency4/5

Most tools follow 'web_fetch_*' pattern (chunked, code, links, section, tables), but 'web_preflight' and 'web_smart_fetch' deviate slightly. Still readable.

Tool Count5/5

7 tools cover essential web fetching operations without redundancy. The count is well-scoped for a focused utility server.

Completeness4/5

Common use cases (full page, paginated, sections, tables, links, code) are covered. Missing advanced selectors (CSS, XPath) but core needs are met.

Maintenance

ActivityInactive
ResponsivenessNo issues