Skip to main content
Glama

Trace request path

trace_request_path
Read-only

Trace a URL end to end and name the FIRST broken hop with evidence. Call this FIRST for any 'URL / preview / demo / ingress / hostname does not work', 502/503/504, timeout, 404 from the ingress controller, or certificate error symptom: it walks DNS (resolved addresses or NXDOMAIN, and for a hostname under an Ankra-managed zone which cluster owns it, whether an external-dns publisher is installed, whether it is running and whether its webhook provider has endpoints), TCP connect, the TLS handshake and certificate (issuer, SANs, expiry, verification error), the HTTP answer (status, server, redirect, body snippet), then inside the cluster the Ingress, IngressRoute or HTTPRoute whose host rule matches (namespace, backend Service and port, TLS secret, load balancer address versus DNS), the cert-manager Certificate and its ACME challenge, the backend Service (type, selector, ports), its ready and not-ready endpoints, and the Pods behind it (phase, ready, restarts, waiting or terminated reason, the last log lines of the first not-ready pod). Every hop records status ok/failed/unknown/skipped, its source (live, or the resource index with its staleness) and elapsed_ms. The verdict names the first failed hop, its cause in one sentence, and the later hop that explains it when there is one - so answer from the verdict without further reads; add at most one or two reads only when a hop is unknown. An unknown hop is a read that did not happen, never a finding. The cluster is derived from the hostname's managed zone, else from a route host match across your readable clusters, else the session's cluster; pass cluster_name or cluster_id to pin it and namespace to narrow the route search. Read-only; the probe dials from the Ankra platform, so private addresses are refused. Whole trace under 15 seconds.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL the user reports as not working: https://host/path, http://host:port/, or a bare hostname (https is assumed).
namespaceNoNamespace to search for the Ingress rule in. Optional; narrows a large cluster.
cluster_idNoUUID of the cluster to read from; an alternative to cluster_name.
cluster_nameNoExact name of the cluster to read the Ingress, Service, endpoints and Pods from. Optional: derived from the hostname's managed zone or an Ingress host match when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint it discloses that the probe dials from the Ankra platform so private addresses are refused, that the whole trace runs under 15 seconds, that each hop carries status/source/staleness/elapsed_ms, and that an unknown hop is a missing read rather than a finding. Those are non-obvious behavioral traits an agent could otherwise misread as evidence.

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?

Purpose, triggers and stop rule are front-loaded in the first two sentences, and there is no filler. The hop inventory is a long dense run-on that could be trimmed, but each clause maps to a real diagnostic layer the agent may need to reason about an unknown verdict.

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?

With no output schema, the description still specifies the return shape: verdict with first failed hop and one-sentence cause, per-hop statuses, source/staleness and timing. Cluster derivation, probe origin and the private-address limitation are all covered, leaving nothing essential for a correct call unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so fields are already documented; the description adds the resolution order the schema does not state (managed zone, then route host match across readable clusters, then session cluster). It also frames namespace as a performance narrowing for large clusters rather than a correctness requirement.

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?

"Trace a URL end to end and name the FIRST broken hop with evidence" gives a specific verb, resource and distinct output (the first broken hop), not just a restatement of the name. The enumerated hop chain makes clear this is a cross-layer ingress/DNS/TLS/HTTP diagnostic, which separates it from the create/apply/list siblings.

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

Usage Guidelines5/5

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

It names exact trigger symptoms (502/503/504, timeout, ingress 404, certificate error) and states "Call this FIRST" for them, plus a stop rule: "answer from the verdict without further reads; add at most one or two reads only when a hop is unknown." That covers when-to-use, when-to-stop, and implicitly that this precedes narrower per-resource reads.

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.