Skip to main content
Glama
Sign In
netloc8-mcp

netloc8-mcp

Official
by netloc8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Get Subnet

get_subnet
Read-onlyIdempotent

Derive the /24 CIDR prefix from an IPv4 address; for IPv6 or invalid inputs, get an explanation why no /24 subnet applies. Runs locally with no API calls.

Instructions

Derive the /24 CIDR prefix from an IPv4 address (e.g. 8.8.8.8 → 8.8.8.0/24). For IPv6 or invalid addresses, returns a message explaining why no /24 subnet applies. Runs locally — no API call, no quota usage.

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

Input Schema

NameRequiredDescriptionDefault
ipYesthe IPv4 or IPv6 address to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds value by confirming local execution (no API/quota) and handling of IPv6/invalid inputs, which goes beyond structured metadata.

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?

Description is two concise sentences. The first sentence directly states the primary function with an example; the second covers edge cases and execution context. No unnecessary words.

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 simple computational tool with 1 parameter and no output schema, the description covers purpose, edge cases, and execution constraints (local, no quota). All essential information is present.

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% with a description for the 'ip' parameter. Description adds meaning by explaining the result is a computed /24 for IPv4 and an error message otherwise, providing context beyond the schema alone.

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 the tool derives a /24 CIDR prefix from an IPv4 address with an explicit example. It also specifies behavior for IPv6/invalid addresses, distinguishing it from sibling tools that perform geolocation or validation.

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?

Description mentions local execution and no quota usage, implying use when network call avoidance is desired. However, it does not explicitly state when not to use it or compare to alternatives like validate_ip.

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

Deploy Server

Other Tools