Skip to main content
Glama

BRAINIAC Telecom & Network Infrastructure Intelligence

Build network infrastructure health report

network-intelligence_infrastructure-health-report

Aggregate log, latency, packet-loss, DNS, BGP, certificate, configuration, reputation, and incident sections from caller-supplied network records. Price $0.08 USDC. POST /api/v1/network-intelligence/infrastructure-health-report. 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_infrastructure-health-report"
  }
}

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 carries the full burden, and it does disclose genuinely useful operational facts: the $0.08 USDC price, the POST endpoint, and that unpaid calls return 402 without executing. That is real behavioral context beyond the schema. What it does not disclose is anything about the returned report (section structure, scoring, thresholds), idempotency, or how partial input affects output, leaving the mutation-equivalent burden only partly met.

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, front-loaded with purpose before commercial and transport details. Every sentence carries information. Minor cost: the endpoint path is low-value for an agent that already has the tool registered, while the missing input guidance would have been worth that space.

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?

For a 20-parameter tool with nested objects, no annotations, and no output schema, the description is thin. It never explains what the report actually contains (per-section verdicts? overall score?), how the numerous optional inputs combine, or which fields are needed for a meaningful result — an agent cannot confidently assemble a call from this definition alone.

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. The domain list loosely maps to logs, latencySamples, packetLossSamples, dnsRecords, bgpRoutes, certificates, configs, reputations, and incidents, but the tuning parameters (asOf, latencyAnomalyZ, expiryWarningDays, packetLossWarnPct), the input-mode alternatives (csv, json, text, file, files), and the live-lookup objects (publicDns, publicTls) are never explained.

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 names a specific verb ('Aggregate') and its resource (sections derived from caller-supplied network records), then enumerates the domains covered: logs, latency, packet loss, DNS, BGP, certificates, configuration, reputation, incidents. That enumeration implicitly distinguishes it from siblings such as latency-anomaly-detect or bgp-route-change-analyze, which cover only one domain, though no sibling is named 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?

Usage is implied by the word 'Aggregate' plus the section list — an agent can infer this is the one-shot rollup rather than a single-domain diagnostic. However, there is no explicit statement of when to prefer this over calling the individual sibling tools, and no exclusions or prerequisites (e.g., minimum viable input set) are given.

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