SiteCheck

Redirects

redirects

Read-only

The redirect chain of a URL, hop by hop (at most 10 hops): each URL, its status, the Location it points to, and whether the hop goes from http to https or changes host. Returns the final URL and status, total hops, loop true when a URL repeats, and the Strict-Transport-Security header of the final response. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Input Schema

Name	Required	Description	Default
`url`	Yes	Page URL or domain, e.g. example.com

Output Schema

Name	Required	Description	Default
`url`	No
`hops`	No
`hsts`	No
`loop`	No
`maxHops`	No
`finalUrl`	No
`checkedAt`	No
`totalHops`	No
`truncated`	No
`finalStatus`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "checkedAt": {},
+    "finalStatus": {},
+    "finalUrl": {},
+    "hops": {},
+    "hsts": {},
+    "loop": {},
+    "maxHops": {},
+    "totalHops": {},
+    "truncated": {},
+    "url": {}
+  },
+  "type": "object"
+}

AddedOct 13, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the readOnly and openWorld annotations, the description discloses the 10-hop limit, loop detection behavior, HSTS header inclusion, and a precise pricing model ($0.002 USDC per successful call, failed calls not charged). These are material behavioral traits an agent needs before invoking the 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?

The description is front-loaded with the core behavior and uses compact, information-dense sentences. It is somewhat packed with return-field details and pricing, but every sentence earns its place and nothing is redundant.

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

Completeness5/5

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

Given a single-parameter tool with an output schema and readOnly/openWorld annotations, the description is fully sufficient: it covers scope, hop limits, loop handling, output highlights, and billing. Nothing an agent needs to call it correctly is missing.

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 already documented as accepting a page URL or domain. The description adds no further parameter syntax or format details beyond what the schema provides, 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?

The description states a specific resource and operation: retrieving a URL's redirect chain hop by hop, with a clear cap of 10 hops. It is readily distinguishable from sibling tools like headers, dns, or ssl by its focus on redirect chains, though it does not explicitly name those alternatives.

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 by the description of what the tool returns, but there is no explicit guidance on when to choose this over siblings such as headers or ssl, nor any stated exclusions. Adequate but with clear gaps.

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

All SiteCheck tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.