My IP Help

Look up several IP addresses

bulk_lookup

Read-only

Geolocation, network and risk data (the score with its main reason on every plan; the full breakdown and security flags from Pro) for SEVERAL IP addresses in one call (use this instead of calling lookup_ip repeatedly). Sends them in batches of the plan's bulk size (Free: 20 per request). Each address that returns data counts one lookup against the monthly quota; private, reserved, unknown and duplicate addresses are not counted.

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": {
      "ips": "<ips>"
    },
    "name": "bulk_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`ips`	Yes	The IPv4 or IPv6 addresses to look up (at most 1000).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond readOnlyHint and openWorldHint, the description discloses non-obvious behavior: server-side batching by plan tier and the exact quota-accounting rule, including that private, reserved, unknown and duplicate addresses are not counted. Quota consumption is precisely the kind of side effect the annotations do not cover, so this is substantive added context.

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?

The value proposition and the sibling alternative are front-loaded in the first sentence, and every subsequent clause carries operational information. It is slightly dense with nested parentheses around the free/pro tier differences, but no sentence is wasted.

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 no output schema, the description carries the burden of describing returns, and it does so at the right level (score plus main reason on all plans, full breakdown and security flags on Pro). Combined with batching and quota rules, an agent has everything needed to invoke it correctly.

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% and the single ips parameter is fully documented, so the baseline is 3. The description adds meaning beyond the schema by explaining how individual entries are treated (duplicates, private/reserved/unknown addresses are excluded from counting), which changes how an agent should construct the list.

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 names the resource (IP addresses), the data returned (geolocation, network and risk data) and the key scope qualifier (SEVERAL addresses in one call), and explicitly contrasts itself with the sibling lookup_ip. An agent can distinguish this from lookup_ip without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit selection rule: 'use this instead of calling lookup_ip repeatedly', which tells the agent both when to use this tool and which alternative it replaces. It also discloses a plan-dependent constraint (bulk size, Free tier 20 per request) that affects how the agent should batch calls.

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

All My IP Help 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?