Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Calculate IPv4/IPv6 CIDR details, aggregates and relations

network-exposure_cidr-calculate
Read-onlyIdempotent

Describe, aggregate or relate CIDR blocks without network access. Price $0.02 USDC. POST /api/v1/network-exposure/cidr-calculate. An unpaid call returns the x402 payment terms and does 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-exposure_cidr-calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
aNoa, string. Optional.
bNob, string. Optional.
cidrNocidr, string. Optional.
cidrsNocidrs, array. Optional.
operationNooperation, string. Optional.

Output Schema

NameRequiredDescriptionDefault
inputNoinput. String.
netmaskNonetmask. String.
networkNonetwork. String.
sourcesNosources. Array.
versionNoversion. Number.
hostmaskNohostmask. String.
lastHostNolastHost. String.
addressesNoaddresses. String.
broadcastNobroadcast. String.
firstHostNofirstHost. String.
hostBitsSetNohostBitsSet. Boolean.
limitationsNolimitations. Array.
usableHostsNousableHosts. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, and the description adds genuinely non-obvious behavior: a $0.02 USDC charge and, importantly, that an unpaid call returns x402 payment terms without executing the operation. That payment-gate detail is the kind of thing an agent cannot get from annotations and would otherwise misread as a failed call. It does not cover error modes or whether payment failures are retryable, keeping it at 4.

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 capability and followed by cost and failure behavior; nothing is padded. The literal endpoint path is arguably operational boilerplate, but it is a single clause and useful for debugging, so it does not meaningfully dilute the text.

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?

An output schema exists, so return-value explanation is correctly omitted, but for a five-parameter tool with no required fields the description does not explain the mode-to-parameter mapping, which is the single most important thing an agent needs. Combined with the meaningless schema parameter text, the definition is under-specified for correct invocation despite being cleanly written.

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 coverage is nominally 100%, but the descriptions are pure name restatements ('a, string. Optional.', 'operation, string. Optional.') and carry zero meaning, so the baseline of 3 is not earned here. With all five parameters optional and none documented, the description offers no hint about what 'a' and 'b' are (a second CIDR for the 'relate' mode?) or the valid values of 'operation', leaving an agent unable to construct a call confidently.

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 names three concrete operations on a specific resource ('Describe, aggregate or relate CIDR blocks') plus the offline nature of the computation, which distinguishes it from siblings like ip-list-diff or firewall-rule-analyze. It stops short of a 5 because it never says which of the three modes correspond to the 'operation' parameter values, so the boundary between this tool and a diff/analyze sibling remains partly inferred.

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 when-to-use guidance: nothing tells the agent when to pick describe vs aggregate vs relate, or when to supply a/b versus cidr/cidrs. No alternative sibling is named or excluded, and the only qualifying clause ('without network access') is a property of the tool rather than a selection rule.

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