Skip to main content
Glama

http

Send web requests and inspect status, redirects, headers, body, and DNS/connect/TLS/TTFB timings to debug APIs and endpoints.

Instructions

HTTP request: status, timing (dns/connect/tls/ttfb), redirects, headers, body (JSON pretty).

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

Input Schema

NameRequiredDescriptionDefault
urlYes
bodyNo
jsonNoJSON body
followNo
methodNo
headersNo
insecureNoself-signed ok
max_bodyNo
timeout_sNo
show_headersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it only sketches the return shape. For a tool exposing a free-form 'method' parameter that can issue POST/PUT/DELETE, there is no statement about side effects, redirect defaults, auth handling, or error behavior — all material for an unannotated 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?

A single compact, front-loaded fragment with no filler, and the most important information (HTTP request) leads. It is under-specified rather than verbose, which is a different problem than wasted wording.

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?

With 10 parameters, no output schema, and no annotations, the definition should do much more. The enumeration of returned facets partially substitutes for a missing output schema, but the input surface is effectively undocumented beyond the required url.

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 only 20% across 10 parameters, so the description is expected to compensate, but it does not. Params such as follow, insecure, max_body, timeout_s, show_headers, and the body/json distinction are never explained; 'body (JSON pretty)' hints at output formatting rather than clarifying the input params.

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 identifies a concrete resource (an HTTP request) and enumerates the returned facets: status, timing phases, redirects, headers, body. An agent can tell this is an HTTP client. It stops short of differentiating from siblings such as 'net', and the telegraphic fragment style leaves the verb implicit.

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 when-to-use guidance, no when-not-to-use, and no named alternative among the sibling tools. The agent must infer that this is the general HTTP fetch tool by name alone.

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