Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Summarise Nmap XML or Masscan JSON

network-exposure_nmap-xml-summarize
Read-onlyIdempotent

Turn scan output into host/service risk summaries. Price $0.03 USDC. POST /api/v1/network-exposure/nmap-xml-summarize. 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>",
      "content": "<content>"
    },
    "name": "network-exposure_nmap-xml-summarize"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatYesformat, string, one of nmap_xml, masscan_json. Required.
contentYescontent, string, length 1 to 5000000. Required.

Output Schema

NameRequiredDescriptionDefault
byHostNobyHost. Array.
hostsUpNohostsUp. Number.
sourcesNosources. Array.
byServiceNobyService. Object.
hostsDownNohostsDown. Number.
openPortsNoopenPorts. Number.
limitationsNolimitations. Array.
skippedHostsNoskippedHosts. Number.
riskyServicesNoriskyServices. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses pricing ($0.03 USDC), the POST endpoint, and that an unpaid call returns x402 payment terms without executing. This is meaningful operational context an agent would otherwise lack; return-value details are omitted but an output schema exists.

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 the purpose, followed by cost, endpoint, and payment-gating behavior. Telegraphic but every sentence carries information; no filler.

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?

With two fully documented parameters, complete annotations, an output schema, and explicit payment behavior, the description covers what an agent needs to decide and invoke correctly. Missing only usage guidance relative to sibling tools.

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 description coverage is 100% and the format enum is documented, so the schema carries parameter meaning. The description only implies that content is a scan document and adds no format-specific syntax or size guidance beyond the schema.

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 opening clause states a specific transformation: scan output into host/service risk summaries, and the title names the accepted formats (Nmap XML, Masscan JSON). It does not explicitly differentiate itself from siblings such as port-service-risk-classify, but the verb+resource is unambiguous.

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 guidance on when to use this versus alternatives, nor on prerequisites such as having an existing scan file versus running a scan. Usage is only implied by the phrase 'scan output'.

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