Skip to main content
Glama

Probe latency and test the RTT floor

probe_latency

Measure a host from distributed vantage points to test its physical RTT floor, returning implied maximum distance, anycast verdicts, and FALSIFIED results when a claimed origin is impossible.

Instructions

Measure a host from distributed vantage points and test the physical RTT floor. Returns per-probe implied maximum distance, an anycast verdict, and a FALSIFIED verdict when a measurement is impossible for the claimed 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": "probe_latency"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesHostname or IP to ping.
limitNoProbe count (default 6).
expected_regionNoClaimed cloud region, e.g. "ap-southeast-1".
expected_countryNoClaimed ISO country code, e.g. "CN".
measurement_typeNoDefault ping.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the shape of the results (implied maximum distance, anycast verdict, falsified verdict), which is genuinely useful. It does not say whether the probe actively sends traffic to third-party hosts, whether it can fail or time out, or whether limit affects cost/runtime. Safety and side-effect profile remain undocumented.

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 sentences, front-loaded with the action and followed by the return summary; there is no filler. The second sentence is dense but every clause conveys distinct information about the outputs.

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 five-parameter network probe with no annotations and no output schema, the description covers the intent and the headline outputs but leaves open failure modes, runtime, and how the verdicts are determined or structured. It is adequate to attempt a call but not sufficient to predict behavior confidently.

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%, so all five parameters are already documented in the schema, giving a baseline of 3. The description adds a little meaning by tying expected_region/expected_country to falsified verdicts, but it does not clarify the semantics of limit, measurement_type beyond the enum, or the interaction between a claimed origin and the verdict logic.

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 gives a specific verb and resource ('Measure a host from distributed vantage points') and names the distinctive capability ('test the physical RTT floor'), which differentiates it from a plain ping. It also previews the outputs, so an agent knows this is an analysis tool rather than a raw measurement tool. It stops short of naming any sibling (e.g. trace_endpoint), even though the measurement_type enum overlaps with tracing.

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 rather than stated: the mention of a 'FALSIFIED verdict when a measurement is impossible for the claimed origin' signals the intended scenario (validating expected_region/expected_country claims). There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for plain latency checks.

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