Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

network_ip_range_calculator

Read-onlyIdempotent

Compute IPv4 network details offline: expand CIDR blocks, summarize IP ranges, test membership, or list addresses. No DNS or live network required.

Instructions

IP Range Calculator. Compute IPv4 network details with offline integer arithmetic, no DNS or live network. The operation field selects one of four jobs: 'cidr' expands a CIDR block to its network/broadcast/mask/wildcard, usable host range, host count, class, and private/public flag; 'range' summarises an explicit start and end IPv4 into a total address count; 'check' tests whether an IPv4 falls inside a CIDR block; 'list' enumerates the first N addresses of a CIDR block. Use network_subnet_calculator or network_cidr_calculator instead for general subnet planning and notation conversion, and networking_ipv4_to_ipv6 to convert an address to IPv6. IPv4 only. Read-only, non-destructive, contacts no external service, and rate-limited (100 req/min, 1000/hr anonymous). The result object shape depends on the chosen operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesWhich calculation to run. cidr expands a CIDR block; range summarises start/end IPs; check tests membership; list enumerates addresses.cidr
cidrNoCIDR block in address/prefix form, required for the cidr, check, and list operations. Prefix must be 0-32.
inputNoAlias for cidr accepted only by the cidr operation; cidr takes precedence when both are present.
startIpNoFirst IPv4 address of the range, required for the range operation. Must be less than or equal to endIp.
endIpNoLast IPv4 address of the range, required for the range operation.
ipNoIPv4 address to test for membership, required for the check operation.
limitNoMaximum number of addresses to enumerate for the list operation. Output is truncated to this many.
worker_idNoOptional registered healthy worker peer ID. Omit to use the default master-server behavior.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the calculation succeeded.
operationNoThe operation that was run, echoed back.
resultNoOperation-specific payload (object for cidr/range/list; the check operation instead returns a boolean here).
errorNoError message when success is false.
Behavior5/5

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

Beyond annotations (readOnlyHint, destructiveHint, idempotentHint), description adds rate limits (100 req/min, 1000/hr anonymous), offline computation, and no external dependencies. No contradictions.

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?

Well-structured with front-loaded purpose, but slightly verbose with multiple clauses. Each sentence adds value, though could be more compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given complexity (8 params, 4 operations, output schema), description fully covers behavior, limitations, and usage. No gaps remain for an AI agent to use the tool correctly.

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%, so baseline 3. Description minimally adds context beyond schema (e.g., 'result object shape depends on operation'), but schema already defines each parameter with descriptions and examples.

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?

Description clearly states it's an IP Range Calculator for IPv4 with offline arithmetic. It enumerates four distinct operations (cidr, range, check, list) and distinguishes from sibling tools like network_subnet_calculator and networking_ipv4_to_ipv6.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use each operation via the 'operation' field. Provides alternatives for subnet planning and IPv6 conversion. States 'IPv4 only' and 'no DNS or live network', setting clear boundaries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server