Skip to main content
Glama

Web fetch

web_fetch
Read-only

Fetch content from a public HTTPS URL and return it as readable text. Use this to look up documentation, release notes, Helm chart READMEs, Kubernetes docs, or any public web page the user references. SECURITY: Only HTTPS URLs on public hosts are allowed. Requests to private/internal IPs (10.x, 172.16-31.x, 192.168.x, 127.x, localhost, [::1]) and non-HTTPS schemes are rejected.

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": "web_fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe HTTPS URL to fetch. Must be a public, HTTPS-only URL. No local/private IPs allowed.
max_lengthNoMaximum number of characters to return. Defaults to 8000.
extract_modeNoHow to extract content: 'text' strips HTML to readable text (default), 'html' returns raw HTML, 'raw' returns the response body as-is.text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety burden is partly lifted, and the description still adds a genuinely useful SECURITY paragraph: HTTPS-only, rejection of private/internal ranges (10.x, 172.16-31.x, 192.168.x, 127.x, localhost, [::1]) and non-HTTPS schemes. It omits other behaviorally relevant facts such as timeouts, redirect handling, or truncation semantics tied to max_length.

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?

Three sentences: purpose and return type first, usage examples second, hard security constraints last. No filler, no repetition of the title, and the constraint block is clearly demarcated so an agent can skim to the operative rules.

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?

With no output schema, the description usefully states that the return is readable text, and the security restrictions cover the main failure mode an agent would hit. For a 3-parameter read-only fetch tool this is close to complete, with only edge behavior (size limits, redirects, error responses) left unspecified.

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

Parameters3/5

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

Schema description coverage is 100%, so url, max_length, and extract_mode are already documented in the schema. The description only loosely gestures at extract_mode by promising 'readable text', and adds nothing about max_length truncation or when to prefer html/raw modes. Baseline 3 applies when the schema does the heavy lifting.

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?

The description opens with a specific verb+resource+output shape: 'Fetch content from a public HTTPS URL and return it as readable text.' That distinguishes it from internal readers like workspace_read_file or github_read_file by scoping to public web pages, though it never names those siblings explicitly.

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?

It gives concrete when-to-use cases (documentation lookup, release notes, Helm chart READMEs, Kubernetes docs, any public page the user references), which is strong positive guidance. It does not explicitly state when NOT to use it versus siblings such as github_read_file or probe_endpoint, so the routing is implied rather than declared.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.