Skip to main content
Glama

Trace an endpoint

trace_endpoint

Resolve a hostname into its serving chain—CNAME hops, IP addresses, ASN/org, RDAP, and cloud region—and flag CDN/anycast addresses so edge PoPs aren't mistaken for origins.

Instructions

Resolve one hostname into a serving chain: CNAME hops, addresses, ASN and org, registry RDAP, and the published cloud region of each address. Flags CDN/anycast addresses so an edge PoP is never mistaken for an origin.

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": {
      "host": "<host>"
    },
    "name": "trace_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesHostname or URL, e.g. "api.deepseek.com".
max_ipsNoHow many addresses to enrich (default 3).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it well: it discloses the enrichment stages performed (ASN/org, RDAP, cloud region) and the CDN/anycast flagging that prevents mistaking an edge PoP for an origin. It omits operational traits such as whether queries are live network calls, rate limits, or what happens for unresolvable hosts, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both front-loaded with the highest-value information: the resolution verb and scope first, then the interpretation caveat about edge PoPs. No filler, no restatement of the title, and the enumeration is compact.

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?

With only two simple parameters and no output schema, the description usefully enumerates what the tool returns, which is exactly the gap an absent output schema leaves. The remaining shortfall is failure behavior and cost/latency expectations for a tool that presumably performs live lookups.

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%, so both parameters (host, max_ips) are fully documented in the schema and the baseline is 3. The description adds only that exactly one hostname is resolved, and says nothing about how max_ips bounds enrichment depth or what a URL-form host is normalized to.

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 opens with a specific verb and resource ('Resolve one hostname into a serving chain') and enumerates exactly what that chain contains: CNAME hops, addresses, ASN/org, RDAP, and cloud region. An agent can tell this is a per-host DNS/infrastructure trace. It stops short of naming a sibling such as lookup_prefix or locate_model to draw a hard boundary, so a 4 rather than 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 Guidelines3/5

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

Usage is only implied: 'Resolve one hostname' signals single-host scope versus fleet-wide siblings like observe_endpoints or fleet_status, but the description never states when to choose this tool or when another is preferred. There is no explicit exclusion or precondition, leaving the agent to infer routing from scope language alone.

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