Skip to main content
Glama

BRAINIAC Telecom & Network Infrastructure Intelligence

Analyze packet-loss patterns

network-intelligence_packet-loss-pattern-analyze

Analyze caller-supplied packet-loss percent or sent/lost counts against a warning threshold. Price $0.03 USDC. POST /api/v1/network-intelligence/packet-loss-pattern-analyze. 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_packet-loss-pattern-analyze"
  }
}

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.1/5.0
Behavior3/5

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

With no annotations, the description does useful work: it discloses price ($0.03 USDC), the POST endpoint, and that unpaid calls return 402 without executing. It does not say whether the operation is read-only, how the threshold comparison is reported, or what the response contains, which matters for a compute tool with no output schema.

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?

Four short sentences, front-loaded with what is analyzed, then cost, endpoint, and payment failure mode. The endpoint path largely restates the tool name, a minor redundancy, but nothing else is wasted.

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?

A 20-parameter tool with nested objects, no output schema, and no annotations needs more explanation than this. The agent knows the price and the core metric, but not which of the many input channels to populate or what analysis it gets back.

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 and largely does not. It clarifies only the packet-loss inputs (lossPct, sent/lost, packetLossWarnPct); the other data-source parameters (csv, json, text, files, logs, configs, bgpRoutes, incidents, publicDns, asOf) receive no explanation of format or role.

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?

States a specific verb ('Analyze') plus the exact resource and computation: caller-supplied packet-loss percent or sent/lost counts measured against a warning threshold. That is enough to distinguish it from siblings like latency-anomaly-detect, though it never names them explicitly.

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?

Implies usage through 'caller-supplied,' telling the agent it must bring its own sample data rather than query a live network, and the 402 note signals payment is a precondition. It gives no when-to-use/when-not guidance relative to related tools such as latency-anomaly-detect or infrastructure-health-report.

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