Skip to main content
Glama

http_fetch

Send custom HTTP requests to retrieve URL status, headers, and body; report binary response sizes and optionally disable TLS verification for broken certificates.

Instructions

Fetch a URL with custom method/headers/body and return status, headers and body.

headers is a JSON object string, e.g. '{"Authorization": "Bearer x"}'. Binary responses are reported with size instead of content. TLS verification can be disabled for targets with broken certificates.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
bodyNo
methodNoGET
headersNo
max_charsNo
verify_sslNo
include_bodyNo
follow_redirectsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses return shape (status, headers, body), binary-response handling, and that TLS verification is defeatable, which are real behavioral facts an agent could not get elsewhere. But it never says that an arbitrary `method` means this tool can issue mutating requests (POST/PUT/DELETE), nor does it mention timeouts, rate limits, or auth expectations — significant gaps for an unannotated network tool.

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

Conciseness4/5

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

Four short sentences with the core capability front-loaded and the format example placed where it is needed. Little waste, though the headers example is slightly verbose for what it conveys.

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

Completeness2/5

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

An 8-parameter, unannotated, no-output-schema tool with 0% schema coverage needs a much fuller description. Missing explanations for three boolean/integer knobs, no statement of mutation risk from arbitrary methods, and no error/timeout behavior leave an agent guessing on how to call it safely.

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

Parameters2/5

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

Schema description coverage is 0% across 8 parameters, so the description must compensate and only partly does: it explains `headers` as a JSON object string with a concrete example, implies `method`/`body`, and hints at `verify_ssl` and binary handling. It says nothing about `max_chars`, `include_body`, `follow_redirects`, or `url` semantics, leaving four of eight parameters undocumented anywhere.

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 specific verb and resource: fetch a URL with custom method/headers/body, returning status, headers and body. That is unambiguous about what the tool does. It stops short of distinguishing itself from siblings like http_headers_audit or browser_open, so an agent must infer that this is the generic raw HTTP client.

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

Usage Guidelines2/5

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

There is no statement of when to use this rather than http_headers_audit, browser_open or api_discovery, and no exclusions or prerequisites. The only conditional hint ('TLS verification can be disabled for targets with broken certificates') is parameter-level guidance, not tool-selection guidance.

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