mcp-ip2location

Bulk IP Geolocation

bulk_geolocate

Geolocate up to 50 IP addresses in a single request and receive a compact table with their locations. Ideal for analyzing IPs from log files.

Instructions

Geolocate up to 50 IP addresses in a single request and return a compact table. Useful for analyzing a list of IPs from a log file.

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_geolocate"
  }
}

Input Schema

Name	Required	Description	Default
`ips`	Yes	List of IP addresses (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 31, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions the batch limit (already in schema) and the compact table return format, but does not disclose error handling, invalid IP behavior, or latency characteristics. The added value is modest.

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 a single concise sentence plus a usage tip, with zero fluff. It front-loads the core functionality and limit in the first clause.

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?

Given the simple tool (one parameter, no output schema, no annotations), the description covers the essential purpose and a typical use case. It lacks detail about the actual table columns or failure modes, but for a batch geolocation tool, it is reasonably complete.

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% (the 'ips' parameter has a description: 'List of IP addresses (max 50)'). The tool description adds only the redundant 'up to 50 IP addresses' detail and does not elaborate on IP format (IPv4/IPv6) or input requirements beyond the schema.

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 clearly states the tool's action ('Geolocate'), the resource ('IP addresses'), the batch scope ('up to 50 in a single request'), and the output format ('compact table'). It also distinguishes itself from single-IP siblings like ip_geolocation through its batch focus.

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?

The description provides a clear use case ('analyzing a list of IPs from a log file') but does not explicitly exclude single-IP usage or mention alternatives (e.g., ip_geolocation). This is clear context without explicit when-not-to-use guidance.

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

Deploy Server