Skip to main content
Glama

BRAINIAC Telecom & Network Infrastructure Intelligence

Detect network latency anomalies

network-intelligence_latency-anomaly-detect

Detect anomalous latency using z-scores on caller-supplied path samples. No active probing of private networks. Price $0.03 USDC. POST /api/v1/network-intelligence/latency-anomaly-detect. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "network-intelligence_latency-anomaly-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
logsNo
textNo
filesNo
configsNo
bgpRoutesNo
incidentsNo
publicDnsNo
publicTlsNo
dnsRecordsNo
reputationsNo
certificatesNo
latencySamplesNo
latencyAnomalyZNo
expiryWarningDaysNo
packetLossSamplesNo
packetLossWarnPctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description discloses important behavior: z-score methodology, no active probing of private networks, a $0.03 USDC price, POST endpoint, and that unpaid calls return 402 without running. However, it does not describe read-only status, rate limits, error behavior beyond 402, or what the result contains.

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?

The description is short and front-loaded: purpose first, then scope constraint, price, endpoint, and unpaid-call behavior. Every sentence carries operational or behavioral information, with no filler.

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

Completeness2/5

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

This is a complex tool with 20 nested parameters, no schema descriptions, no annotations, and no output schema. The description gives a high-level purpose and payment behavior but leaves an agent without guidance on which input parameters to use or what the output will look like.

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

Parameters2/5

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

Schema description coverage is 0% across 20 parameters, so the description must compensate, but it only vaguely mentions caller-supplied path samples and z-scores. It does not explain latencySamples, latencyAnomalyZ, packetLossSamples, csv/json/text, logs, configs, bgpRoutes, or the many other accepted inputs.

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 states a specific verb and resource: detect anomalous latency using z-scores on caller-supplied path samples. It is clear enough to distinguish this as a latency analysis tool, but it does not explicitly differentiate it from the packet-loss-pattern-analyze sibling or other network-analysis tools.

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?

The description says input must be caller-supplied path samples and that no active probing of private networks is performed, but it gives no when-to-use guidance or alternatives. An agent is not told when to choose this over packet-loss analysis or other sibling diagnostics.

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