Skip to main content
Glama

Sitesy Website Intelligence

Redirect trace

redirect_trace
Read-onlyIdempotent

Every hop a web address takes, with each status code and destination. Costs 0.001 USDC per call. The caller pays per call in USDC on Base through x402: the first call returns the payment requirements, and an x402 aware MCP client signs and retries automatically.

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

Input Schema

NameRequiredDescriptionDefault
urlYesA web page address, for example https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and non-destructive, and the description adds genuinely non-obvious behavior on top: a fixed 0.001 USDC cost per call, payment on Base via x402, and the two-phase flow where the first call returns payment requirements and an x402-aware client signs and retries. That payment handshake is exactly the kind of operational trait annotations cannot convey and that would otherwise cause a naive agent to treat the first response as an error.

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?

Two tight sentences: output content first, then cost and payment mechanics, with no filler. The payment sentence is long but every clause is actionable; only the missing verb in the opening fragment slightly weakens front-loading.

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 one-parameter read-only tool with no output schema, the definition covers purpose, cost, and the x402 retry protocol well enough to invoke correctly. It stops short of edge behavior — maximum hops followed, handling of invalid or non-HTTP URLs, and whether the trace aborts on loop detection — which would matter for a redirect tracer.

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% with a single documented `url` parameter (format uri, maxLength 2048, example provided), so the schema already carries full parameter meaning. The description adds nothing about the URL beyond that — no notes on redirect limits, scheme handling, or what happens with a non-resolving address — so baseline 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?

"Every hop a web address takes, with each status code and destination" names the exact resource and returned data: the HTTP redirect chain with per-hop status codes and targets. It is a noun phrase rather than a verb+resource statement, and it does not name or distinguish any sibling tool, so it falls 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 Guidelines2/5

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

There is no statement of when to use this versus alternatives (e.g., a page reader or site check) and no exclusions or prerequisites about the input URL. The only invocation guidance is about payment, not about task selection, so the agent must infer usage from the name alone.

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