net-mcp

Subnet Split

subnet_split

Split an IP prefix into smaller subnets for both IPv4 and IPv6, enabling network segmentation by breaking down large blocks into a desired prefix length.

Instructions

Split an IP prefix into smaller subnets.

For example, split 10.0.0.0/24 into /26s to get 4 subnets. Works with both IPv4 and IPv6.

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": {
      "prefix": "<prefix>",
      "new_prefix_length": "<new_prefix_length>"
    },
    "name": "subnet_split"
  }
}

Input Schema

Name	Required	Description	Default
`prefix`	Yes	IP prefix to split (e.g. '10.0.0.0/24')
`new_prefix_length`	Yes	New prefix length for subnets (must be longer than current)

Output Schema

Name	Required	Description
`total`	Yes	Total subnet count; a decimal string when it exceeds 2^53 (large IPv6 splits)
`subnets`	Yes
`original`	Yes
`new_prefix_length`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 22, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are present, so the description carries the behavioral disclosure burden. It adds useful context by stating 'Works with both IPv4 and IPv6' and providing a concrete example, but it does not describe the output format or behavior on invalid inputs. For a simple pure computation this is adequate, though not rich.

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 with no wasted words: purpose, example, and protocol support. The key information is front-loaded and every sentence earns its place.

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?

For a low-complexity pure function with two clearly documented parameters and an output schema, the description covers the essential selection and invocation details. The example plus protocol coverage makes it complete enough for an agent to call correctly.

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

Parameters4/5

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

Schema coverage is 100%, so parameters are already documented. The description adds value by giving a concrete example that maps prefix and new_prefix_length to an expected result ('4 subnets'), which helps an agent understand the relationship between parameters beyond the schema.

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+resource: 'Split an IP prefix into smaller subnets.' The example (splitting 10.0.0.0/24 into /26s) and the IPv4/IPv6 note make the tool's purpose unambiguous and clearly distinguish it from sibling tools like supernet_aggregate or subnet_info.

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 to use the tool through its purpose and example, but it does not explicitly contrast it with siblings such as supernet_aggregate or subnet_info. There is no when-to-use vs. when-not-to-use guidance, though the use case is clear enough on its own.

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