GadgetHumans API Hub

cidr_calc

Expand a CIDR block into network address, broadcast, netmask, wildcard, usable host range and host count. Pure CPU, instant. Use to plan a subnet or test whethe

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": {
      "cidr": "<cidr>"
    },
    "name": "cidr_calc"
  }
}

Input Schema

Name	Required	Description	Default
`cidr`	Yes	CIDR block such as 10.0.0.0/24

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026
RemovedNov 6, 2026

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / cidr

Added value: +{
+  "description": "CIDR block such as 10.0.0.0/24",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "cidr"
+]
```

AddedNov 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations, so the description carries the full burden. 'Pure CPU, instant' usefully signals that this is a side-effect-free, non-network computation, which is the main behavioral trait an agent needs. It does not explicitly state that no state is changed or what the response shape looks like, so coverage is partial rather than complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is dense and front-loaded with the useful output list, and 'Pure CPU, instant' is efficiently terse. However the final sentence is a dangling fragment, which is wasted space and reads as a defect rather than concision.

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?

With no output schema, the description compensates by naming the six values returned, which is the key missing information for this tool. The only real gap is the truncated usage clause, and the tool is simple enough that an agent can call it correctly from what is present.

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?

Only one parameter, and the schema already documents it fully with a format example ('10.0.0.0/24') at 100% coverage. The description adds no syntax rules such as prefix-length bounds or IPv6 support. Baseline 3 applies when the schema does the work.

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 opens with a specific verb and resource ('Expand a CIDR block') and enumerates the derived values returned (network address, broadcast, netmask, wildcard, host range, host count). That is enough for an agent to tell it apart from neighbors like ipv4_validate or ip, which check or look up rather than expand.

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?

There is a use-case clause ('Use to plan a subnet or test whethe'), but it is cut off mid-sentence, so the alternative it was meant to name never appears. The tool is a utility with no real siblings competing for the same job, which limits the damage, but the guidance is incomplete as written.

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

All GadgetHumans API Hub tools Inspect

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.