Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Analyse firewall rules for anomalies

network-exposure_firewall-rule-analyze
Read-onlyIdempotent

Find shadowed, redundant and overly permissive iptables/nftables/AWS SG rules. Price $0.04 USDC. POST /api/v1/network-exposure/firewall-rule-analyze. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "format": "<format>",
      "rules": "<rules>"
    },
    "name": "network-exposure_firewall-rule-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesYesrules, value. Required.
formatYesformat, string, one of iptables, nftables, aws_sg. Required.
sensitivePortsNosensitivePorts, value. Optional.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
findingsNofindings. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds genuinely useful behavior beyond them: the cost ($0.04 USDC) and the x402 unpaid-call behavior that returns payment terms without executing. It doesn't describe output content, but an output schema exists to cover that.

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 compact, front-loaded sentences with no filler; the core capability leads and payment behavior follows. The explicit POST path is somewhat redundant with the tool name but is arguably useful for direct API callers.

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?

For a read-only analysis tool with a full input schema and an output schema, the description covers purpose, cost, and payment gate behavior adequately. Minor gaps (no note on output/result shape or limits on rule-set size) are low-impact given the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents format, rules, and sensitivePorts. The description mentions the three format values but adds no syntax or shape guidance beyond the schema, so the baseline 3 applies.

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 ('Find') and specific findings ('shadowed, redundant and overly permissive') across three explicit rule formats (iptables/nftables/AWS SG). Clear purpose without ambiguity, though it doesn't explicitly differentiate from any sibling (which is fine since the sibling set covers unrelated analysis utilities).

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 description implies when the tool is useful (auditing firewall rule sets for anomalies) but offers no explicit when-to-use/when-not guidance or alternatives to prefer for other exposure analyses. The pricing and payment details describe invocation mechanics rather than usage 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