Skip to main content
Glama
websearch-mcp

websearch-mcp

by xronocode

fetch

Read-onlyIdempotent

Retrieve public web pages or text-based PDFs as readable, token-efficient text with links and tables preserved, using local caching and no API keys.

Instructions

Free LOCAL URL fetch, no provider quota: GET the page and return readable text. HTML pages -> extracted main content with links and tables kept (much fewer tokens than raw dump); PDF -> extracted text (text-based PDFs only, scanned need OCR). Only public http/https URLs; redirects are vetted hop by hop; response capped at 20 MB, maxlen capped at 30000. Cached locally for 7 days. If a page yields almost no text (JS-rendered or blocked), returns a note to use browser automation for that URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
maxlenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.3/5.0
Behavior5/5

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

Well beyond the annotations (readOnly/openWorld/idempotent/non-destructive), it discloses redirect vetting hop by hop, a 20 MB response cap, a 30000 maxlen ceiling, a 7-day local cache, and the graceful-degradation note returned when extraction yields almost no text. These are exactly the operational facts an agent needs to predict success or failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Front-loaded with the key fact (free, local, no quota), then content-type behavior, then constraints, then the failure fallback. Arrow notation and parentheticals pack a lot into few lines with no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the description covers access restrictions, size limits, caching, and degraded cases. The only shortfall is the unspecified maxlen unit and truncation semantics, which matter for a tool whose main cost lever is output length.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the load, and it does for 'url' by restricting it to public http/https and warning that redirects are vetted per hop. For 'maxlen' it adds a meaningful ceiling of 30000, but never states the unit (characters of extracted text) or what truncation looks like, leaving one gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ('GET the page and return readable text') plus the output shape per content type (HTML -> extracted main content with links/tables; PDF -> extracted text). This clearly separates it from the search* siblings, which discover URLs rather than retrieve page content. It never names a sibling explicitly, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real selection context: use it for token-efficient retrieval of a known URL, restricted to public http/https, text-based PDFs only, and it explicitly routes JS-rendered/blocked pages to browser automation. It does not name the search siblings as the way to obtain a URL in the first place, so the when-not/alternative coverage is partial rather than exhaustive.

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