Skip to main content
Glama

Redirect Checker API - redirect chain, status codes, HTTP headers

redirect_checker
Read-onlyIdempotent

Follow a URL hop by hop: every redirect with status (301/302/307/308), Location, response time and server, the final URL and status, all response headers, security headers present (HSTS, CSP, X-Frame-Options...) and plain-English issues (too many hops, 302 instead of 301, no http->https). Live, ~1 s. Free: 25 calls/day per IP. Paid: $0.002 per call via x402 at https://radarbg.com/x402/redirect-checker.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "http://github.com"
    },
    "name": "redirect_checker"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL or domain, e.g. http://github.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld and idempotent, so the safety profile is covered; the description adds materially beyond that with latency (~1 s live fetch), free-tier rate limit (25 calls/day per IP) and paid x402 pricing at a specific endpoint. It does not state what happens on unreachable/invalid hosts or whether errors consume quota, which is the main residual gap.

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?

Front-loaded with the core action, then output inventory, then operational/pricing facts — a sensible order with no filler sentences. The header enumeration is slightly dense but each listed item maps to an actual return field, so little is wasted.

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?

There is no output schema, so the description must describe results, and it does so thoroughly — hop-level data, final status, headers, security headers and issue summaries. Combined with pricing and latency, an agent can decide and call correctly; only error/failure behavior remains 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% and the single 'url' parameter is documented with a concrete example, so the description is not required to carry parameter meaning. It adds only the implicit hint that a bare domain is acceptable ('URL or domain' appears in the schema, not the description), leaving the baseline 3 appropriate.

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

Purpose5/5

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

States a specific verb and resource — 'Follow a URL hop by hop' — and enumerates exactly what the tool returns (per-hop status 301/302/307/308, Location, timing, server, final URL, headers, security headers, plain-English issues). That framing cleanly separates it from nearby siblings such as domain_intel, domain_security_report or security_scan, which are about domain/security posture rather than redirect chains.

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 implied rather than prescribed: the enumeration of redirect diagnostics tells an agent what the tool is for, but there is no explicit when-to-use/when-not or pointer to a sibling for deeper security analysis. The only explicit constraints given are operational (live check, ~1 s, 25 calls/day free, $0.002 paid), not selection guidance.

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.

Resources