Skip to main content
Glama

net-web-media

ipv4_subnet_calculate

Compute IPv4 CIDR network address, broadcast address, netmask, wildcard mask, usable host range, and private RFC1918 classification.

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": "ipv4_subnet_calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidrNo192.168.10.25/24
textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a pure, side-effect-free computation but never says so, and it is silent on invalid-CIDR handling, what happens when no argument is supplied, or that both parameters are optional with a fallback default.

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?

A single tight sentence with the return values front-loaded and no filler. It is under-informative rather than bloated, so there is nothing to trim.

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

Completeness3/5

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

With no output schema, naming the returned fields is genuinely valuable and largely covers the return side. However, for a two-parameter tool with one unexplained parameter and no annotations, the definition leaves too much for the caller to guess.

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 description coverage is 0%, so the description must compensate and does not: it never explains the expected 'cidr' format or that 'text' exists at all, leaving one of two parameters completely unmotivated. The schema's default value hints at the CIDR shape but the description adds nothing beyond it.

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?

States a specific verb ('compute') and resource ('IPv4 CIDR') and enumerates the exact values produced (network, broadcast, mask, host range). That output list distinguishes it from ipv4_cidr_range_expand in practice, though no sibling is named explicitly.

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 or when-not-to-use guidance, and no routing to the obvious alternative ipv4_cidr_range_expand for expanding a range into individual addresses. The agent must infer from the output list alone whether this is the right tool.

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