Skip to main content
Glama

Caelara Labs SEO & GEO Readiness

redirect_chain_tracer

Trace a redirect chain hop by hop with loop detection and status issues

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

Input Schema

NameRequiredDescriptionDefault
urlYesStarting URL
max_hopsNoMax hops 1-10 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden, and it does add real behavior beyond the name: loop detection and surfacing status issues at each hop. It is silent on whether a live network fetch occurs, timeout/permission behavior, or how the chain is returned, which matters for an unannotated tool with no output schema.

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 front-loaded sentence with no filler; the capability list follows the core purpose directly. It stops just short of being too terse to be self-sufficient.

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

Completeness3/5

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

For a simple two-parameter tool with no output schema, the description covers the essential purpose and two notable behaviors (loop detection, status reporting). It leaves the agent guessing about return structure and network behavior, which is a meaningful gap when no annotations or output schema exist to fill it.

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 coverage is 100% and both parameters (url, max_hops) are documented there, so the baseline is 3. The description adds only the loose notion of 'hop by hop' and does not explain max_hops or what happens when the cap is hit mid-chain.

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 ('trace a redirect chain') plus two concrete capabilities: hop-by-hop walk, loop detection, and status issue reporting. An agent can tell this apart from broken_link_scanner, though the description never explicitly names that sibling as the alternative.

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?

No explicit when-to-use or when-not-to-use guidance and no named alternatives, so the agent must infer that this is for diagnosing a single URL's redirect path versus a site-wide link crawl. The narrow purpose makes the intended usage strongly implied rather than stated.

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