Skip to main content
Glama

ramadasmr-networkcalc-mcp

by ai.smithery
OverviewDiscussionsAdmin

calculate_subnet

Fetch Subnet info for a given ipaddress/subnet/CIDR

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subnetYesIP address, subnet, or CIDR notation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / subnet / description
      Added value: +"IP address, subnet, or CIDR notation"
    • removedInput schema / properties / subnet / title
      Removed value: -"Subnet"
    • removedInput schema / title
      Removed value: -"calculate_subnetArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "calculate_subnetOutput",
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure burden. It fails to indicate whether this performs local calculation or external queries, what the return format contains, or error handling for invalid CIDR notation.

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?

Extremely concise at 8 words in a single sentence. Every word earns its place with the action verb front-loaded. No redundant or filler text present.

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

Completeness2/5

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

For a calculation tool with no output schema, the description inadequately describes the return value. 'Subnet info' is ambiguous—users need to know if this returns network/broadcast addresses, usable IP ranges, or mask conversions to select this 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 coverage is 100% with the 'subnet' parameter fully documented as accepting 'IP address, subnet, or CIDR notation'. The description essentially mirrors this information without adding syntax examples, validation rules, or format preferences, meeting the baseline for well-covered schemas.

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?

The description uses a specific verb ('Fetch') and identifies the resource ('Subnet info'), and specifies acceptable input formats (ipaddress/subnet/CIDR). However, it lacks specificity about what 'info' entails (network ranges, masks, host counts) and does not differentiate from sibling network tools like whois_lookup.

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?

No guidance provided on when to use this tool versus alternatives. Given siblings include other network utilities (dns_lookup, whois_lookup, certificate_info), the description should clarify this performs IP math/calculation rather than external lookups or domain queries.

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

All ramadasmr-networkcalc-mcp 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