Skip to main content
Glama

BRAINIAC Telecom & Network Infrastructure Intelligence

Diff network configurations

network-intelligence_configuration-diff

Diff left/right or before/after network configuration key/value rows from caller-supplied exports. Price $0.03 USDC. POST /api/v1/network-intelligence/configuration-diff. 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_configuration-diff"
  }
}

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

A3.5/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 add real behavioral facts: a $0.03 USDC price, the POST endpoint, and that unpaid calls return 402 without executing. What it omits is what the diff actually returns and how mismatched or missing sides are handled — significant for a 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the operation and its inputs, followed by the two operational facts an agent needs (price, endpoint) and the failure mode. No filler or restatement of the title.

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 no annotations and no output schema, the description is thin: it neither explains how to choose among the numerous input payload types nor characterizes the diff result. The payment and 402 details are covered, but the core input and output contract is not.

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, and the description only gestures at the 'configs' key/value rows and their side values. It says nothing about the many other accepted input shapes (csv, json, text, file/files, logs, bgpRoutes, incidents, publicDns, dnsRecords, reputations, certificates, latencySamples), leaving an agent to guess which payload family to use.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Diff') and a specific resource ('network configuration key/value rows'), plus the accepted comparison framings (left/right, before/after). That resource is clearly distinct from sibling concerns like DNS resolution, reputation, latency, or log normalization, so an agent can pick it without opening the schema.

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?

The phrase 'from caller-supplied exports' implies the caller must bring both sides of the comparison, which is useful context, but there is no explicit when-to-use/when-not guidance and no named alternative among the sibling analysis tools. Usage is inferable rather than stated.

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