Skip to main content
Glama

BRAINIAC Telecom & Network Infrastructure Intelligence

Normalize network logs

network-intelligence_log-normalize

Normalize caller-supplied network/syslog rows. Private addresses in caller data are retained but never contacted. Price $0.03 USDC. POST /api/v1/network-intelligence/log-normalize. 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_log-normalize"
  }
}

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

C2.9/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 behavioral burden, and it does disclose some genuinely useful facts: private addresses are retained but never contacted, the price is $0.03 USDC, and unpaid calls return 402 without executing. However, it is silent on what the normalized output looks like, whether the operation is idempotent, and how the many mutually alternative input formats (csv/json/text/logs/files) interact when several are supplied.

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 with no filler; the core purpose is front-loaded before the privacy, price, and payment details. Given the schema's size, though, the terseness leaves no room for the input-shape guidance that would earn a 5.

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 tool with 20 undocumented parameters, nested objects, no annotations, and no output schema, the description is far too thin. An agent still cannot determine which input container to use or what it will receive back, which is a significant gap for a paid endpoint.

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. "Caller-supplied network/syslog rows" hints that input arrives as records rather than being fetched, but nothing explains the 15-plus other fields such as bgpRoutes, packetLossSamples, asOf, or the precedence between file, files, csv, json, text, and logs.

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 opens with a specific verb and resource: "Normalize caller-supplied network/syslog rows." That is enough to tell an agent this is a formatting/normalization tool rather than the analysis tools among its siblings (bgp-route-change-analyze, latency-anomaly-detect, etc.). It does not explicitly contrast itself with any sibling, so it falls short of a 5.

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 use this tool versus the analyze/diagnose siblings, and no prerequisites or exclusions beyond the payment note. The phrase "caller-supplied" weakly implies it does not fetch data itself, but the agent must infer that.

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