Skip to main content
Glama
Sign In

SmartTools

by io.github.9thShini
OverviewDiscussionsAdmin

Subnet calculator

subnet_calculator

IPv4 subnet details: network, broadcast, mask, wildcard, host range and count for an IP and prefix. Runs on smart-tools.xyz.

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": {
      "ip": "<ip>"
    },
    "name": "subnet_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesIPv4 address, optionally with /prefix (e.g. 10.0.0.1 or 10.0.0.1/8)
localeNoLanguage for the source_url link (default en)
prefixNoCIDR prefix 0–32 (ignored if given in ip)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the IPv4 scope and the output fields, but lacks details on error handling, default prefix behavior, or return format. This is a modest but acceptable level of disclosure for a simple calculator.

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?

The first sentence is concise and informative. The second sentence ('Runs on smart-tools.xyz') adds no value and should be removed, making it slightly less efficient than it could be.

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?

The description lists the output fields, which is useful given no output schema. The schema covers parameters. It could mention edge cases or the return format, but the tool is simple enough that the description is fairly complete.

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?

Input schema coverage is 100%, with clear descriptions for all three parameters. The description's reference to 'IP and prefix' mirrors the schema but adds no new semantic information.

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?

The description clearly states that the tool calculates IPv4 subnet details and enumerates specific outputs (network, broadcast, mask, wildcard, host range, count). This uniquely distinguishes it from sibling calculators.

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

Usage Guidelines4/5

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

The description implies a clear use case: calculating IPv4 subnet information for a given IP and prefix. It doesn't explicitly mention exclusions (e.g., IPv6) or alternatives, but the context is clear enough.

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

All SmartTools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources