ScorpTech x402 Tools

Ip Range Merge

ip_range_merge

Read-onlyIdempotent

Aggregate IP allow/deny lists: merges any mix of IPv4/IPv6 addresses, CIDRs, "a-b" ranges and "ip netmask" entries into the minimal set of CIDR blocks, optionally subtracts an exclude list, reports address counts and tests IPs for membership. For firewall rules, WAF / CDN allowlists and cloud security groups. POST JSON body {items, exclude?, check?}. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/ip-range-merge

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": {
      "items": "<items>"
    },
    "name": "ip_range_merge"
  }
}

Input Schema

Name	Required	Description
`check`	No	IPs to test against the merged result
`items`	Yes
`exclude`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds useful context: it reports address counts, tests membership, requires x402 payment on Solana, and provides an HTTPS endpoint. Exact error and response-shape behavior are not detailed.

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?

The description is front-loaded with the core aggregation behavior, then use cases, request body, pricing, and alternate endpoint. Every sentence adds practical value, with no filler or redundant restatement.

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 covers the key return content by mentioning address counts and membership checks. It also explains payment and an alternate HTTPS endpoint, though it could be more explicit about the full response format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is low at 33%, but the description compensates well. It explains that items accepts mixed IPv4/IPv6 addresses, CIDRs, "a-b" ranges, and "ip netmask" entries; that exclude optionally subtracts ranges; and that check tests IPs for membership.

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?

States a specific verb and resource: aggregates IP allow/deny lists and merges mixed IPv4/IPv6 addresses, CIDRs, ranges, and netmask entries into minimal CIDR blocks. The transformation and optional exclude/membership behavior clearly distinguish it from sibling tools such as cidr_calc.

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?

Gives clear usage contexts such as firewall rules, WAF/CDN allowlists, and cloud security groups. It does not explicitly name when not to use it or compare against alternatives like cidr_calc, but the intended context is evident.

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

All ScorpTech x402 Tools 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.

Resources

Need Help?