Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

CIDR calculator: calculate the address range, size and netmask of a CIDR block

ip_cidr
Read-only

Details of an IPv4 network in CIDR notation: network and broadcast address, first and last usable host, netmask, number of addresses, and whether a given IP falls inside. Use for firewall rules and allowlists. Example: cidr=192.168.1.0/24. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
ipNoOptional IPv4 address to test for membership
cidrYesIPv4 network in CIDR notation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description goes further by disclosing the billing model ($0.01/call via x402 USDC or card key, first 25 free, failed calls free) and by explicitly explaining why repeats cost money despite being pure computation. That resolves the otherwise puzzling idempotentHint=false in terms of charging rather than side effects.

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?

Output fields are front-loaded in the first sentence, followed by use case, example, and pricing; nothing is buried. The pricing/payment sentence is somewhat dense commercial boilerplate, but it carries behavior an agent needs, so it earns its place.

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?

With only two parameters and no output schema, the description compensates by enumerating exactly what is returned and clarifying that the operation is pure computation. Nothing an agent needs in order to select or call this correctly is missing.

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 description coverage is 100%, so both parameters are already documented, and the description's phrasing about an optional IP being tested for membership largely restates the schema's own wording. The one addition is the concrete notation example (192.168.1.0/24), which is minor value on top of a fully documented schema.

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 names the specific resource (an IPv4 network in CIDR notation) and enumerates the computed outputs: network/broadcast address, first/last usable host, netmask, address count, and IP membership. That makes it clearly a subnet-math calculator rather than an IP lookup like ip_info or ip_geolocate, though it never names a sibling explicitly.

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?

"Use for firewall rules and allowlists" gives concrete usage context, and the worked example (cidr=192.168.1.0/24) shows invocation form. There is no when-not-to-use guidance or named alternative, so it stops short of a 5.

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.