Skip to main content
Glama

BRAINIAC Telecom & Network Infrastructure Intelligence

Build network incident timeline

network-intelligence_incident-timeline-build

Build a chronological timeline from caller-supplied incidents and severe log events. Price $0.03 USDC. POST /api/v1/network-intelligence/incident-timeline-build. 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_incident-timeline-build"
  }
}

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 carry real behavioral weight: it discloses the price ($0.03 USDC), the payment failure mode (402, no execution), and the endpoint. However, it says nothing about what the tool actually does with the data — whether it correlates by timestamp across sources, how missing/partial fields are handled, or what the result looks like.

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?

Three short sentences with purpose front-loaded, then cost, then transport and payment failure. No filler, though the endpoint URL arguably duplicates transport metadata that could live in structured fields.

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?

Placeholder.

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?

Twenty parameters with 0% schema description coverage, and the description only vaguely gestures at two input families (incidents, severe log events). Nothing explains asOf, csv/text/json/file(s), configs, bgpRoutes, dnsRecords, reputations, certificates, latencySamples, or the threshold parameters like latencyAnomalyZ, expiryWarningDays, and packetLossWarnPct, so an agent cannot infer which inputs are required or how they interact.

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 and artifact ('Build a chronological timeline') plus the input sources ('caller-supplied incidents and severe log events'), which is enough to distinguish it from a pure normalizer like log-normalize. It stops short of naming or contrasting any sibling explicitly.

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?

There is no statement of when to pick this over siblings such as log-normalize, configuration-diff, or infrastructure-health-report, and no prerequisites for the caller-supplied inputs. The only conditional given is the payment one (unpaid calls return 402), which is about billing, not tool selection.

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