Skip to main content
Glama

Get the raw HTTP response headers of any URL, with status code, final URL after

headers
Read-only

Get the raw HTTP response headers of any URL, with status code, final URL after redirects and response time. Fast (under 2 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.001 per call (x402, USDC on Base).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond them: a latency expectation (under 2 s), a free quota of 20 calls/day, and the overage price with the payment mechanism. It does not explain failure behavior (timeouts, unreachable hosts, non-2xx handling), which keeps it from a 5.

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?

Three compact sentences, front-loaded with what is returned, then speed, then cost. The pricing sentence is long but does carry decision-relevant information for an agent that must decide whether to call it.

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?

For a two-parameter read tool with full schema coverage and no output schema, the description covers purpose, return contents, latency and the paid-retry flow adequately. The remaining gap is error/edge-case behavior, which matters somewhat for an open-world fetch tool.

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%: the url and payment parameters are both documented in the schema, including how to omit payment on the first call. The description adds only the surrounding pricing rationale, so the baseline of 3 applies.

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?

"Get the raw HTTP response headers of any URL" is a specific verb+resource, and the description enumerates the return content (status code, final URL after redirects, response time). It does not explicitly distinguish itself from siblings like status, redirects or security_headers, which overlap in scope, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied by the scope statement — an agent can infer it is the right tool when raw headers are needed. There is no explicit when-to-use versus the closely related status/redirects/security_headers tools, and no exclusions or prerequisites beyond the payment note.

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.