Skip to main content
Glama
Sign In

WhoisFreaks

by io.github.WhoisFreaks
OverviewDiscussionsAdmin

IP geolocation

ipGeolocation
Read-onlyIdempotent

Look up where an IPv4 or IPv6 address is located and which network it belongs to. Use this for country, region, city, coordinates, ISP, ASN, connection type and local currency, for example to localise a visitor or see where a server is hosted. The location is an estimate and is most reliable at country level. For many IPs at once use bulkIpGeolocation. For VPN, proxy, Tor and threat signals use ipSecurity. For the registered owner of the IP block and its abuse contact use ipWhoisLookup. Private and reserved addresses (10.x, 192.168.x, 127.x and similar) cannot be geolocated and return a "non-routable IP" (HTTP 423) message. Behavior: read-only. Makes one request to the WhoisFreaks API using your WhoisFreaks API key (the WHOISFREAKS_API_KEY environment variable, or on the hosted server the key sent with the request) and uses that account's API credits; nothing is created or changed. If the call fails, the result is a short message instead of data, for example: key invalid, or plan or credits used up (HTTP 401), domain extension not supported (HTTP 403), no data found (HTTP 404), or rate limit reached (HTTP 429).

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": {
      "ip": "<ip>"
    },
    "name": "ipGeolocation"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesIPv4 or IPv6 address to geolocate. Examples: 8.8.8.8 | 2606:4700:4700::1111

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations it discloses things they cannot: the API key source (WHOISFREAKS_API_KEY), that calls consume account credits, that nothing is created or changed, and that private/reserved ranges return an HTTP 423 'non-routable IP' message. It also enumerates failure modes (401 invalid key/credits, 403, 404, 429) and the accuracy caveat that results are most reliable at country level.

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?

Front-loads purpose and field coverage, then alternatives, then edge cases, then behavior — a sensible ordering. The HTTP status enumeration is slightly listy but each entry is actionable for error handling, so little 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?

There is no output schema, so the description carries the return shape itself and does so by naming country, region, city, coordinates, ISP, ASN, connection type and local currency, plus what a failure returns. Nothing an agent needs to call and interpret this tool is missing.

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 parameter already carries examples, so the baseline is met by the schema alone. The description adds real meaning by covering both IPv4 and IPv6 support and by warning that private/reserved ranges such as 10.x, 192.168.x and 127.x cannot be geolocated — behavior the schema does not convey.

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 ('look up where an IPv4 or IPv6 address is located and which network it belongs to') and enumerates the returned fields. It explicitly distinguishes itself from bulkIpGeolocation, ipSecurity and ipWhoisLookup, so an agent can route correctly without opening other schemas.

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?

Gives concrete when-to-use framing ('localise a visitor or see where a server is hosted') and names three alternatives with the exact condition that selects each: many IPs -> bulkIpGeolocation, VPN/proxy/Tor/threat -> ipSecurity, block owner/abuse contact -> ipWhoisLookup.

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

All WhoisFreaks toolsInspect
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