Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Diff two host/service exposure snapshots

network-exposure_ip-list-diff
Read-onlyIdempotent

Report new, closed and changed services between before and after snapshots. Price $0.03 USDC. POST /api/v1/network-exposure/ip-list-diff. 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": {
      "before": "<before>",
      "after": "<after>"
    },
    "name": "network-exposure_ip-list-diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterYesafter, array. Required.
beforeYesbefore, array. Required.

Output Schema

NameRequiredDescriptionDefault
newNonew. Array.
closedNoclosed. Array.
changedNochanged. Array.
sourcesNosources. Array.
newHostsNonewHosts. Array.
goneHostsNogoneHosts. Array.
unchangedNounchanged. Number.
duplicatesNoduplicates. Number.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new behavior: the $0.03 USDC price, the HTTP endpoint, and that an unpaid call short-circuits to payment terms without running. It still does not describe how services are matched across snapshots or how 'changed' is determined.

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 output categories, followed by cost and endpoint, then the payment-gating caveat. No redundant or filler wording.

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?

Output schema and annotations are present, so return values and safety need not be restated, and the description covers cost and payment behavior. The one remaining gap is how item identity and change detection work, which affects how an agent should shape the input arrays.

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% for both array parameters, so the schema already documents ip, port, protocol, service, and banner fields. The description adds no extra meaning about how before/after items are keyed or compared, so the baseline of 3 applies.

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 ('Report') with a precise resource ('new, closed and changed services') and names both inputs ('before and after snapshots'). This is clearly a diff operation, distinct from the sibling tools that classify, fingerprint, decode, or validate individual artifacts.

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 diff framing, and the payment note clarifies that an unpaid call only returns x402 terms without executing. However, there is no explicit statement of when to prefer this over alternatives or what prerequisites the snapshots must satisfy (e.g., must they be ordered or pre-filtered).

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