Skip to main content
Glama
Sign In

WhoisFreaks

by io.github.WhoisFreaks
OverviewDiscussionsAdmin

ASN WHOIS lookup

asnWhoisLookup
Read-onlyIdempotent

Get the registry WHOIS record for an autonomous system (ASN): the network operator behind a set of IP routes. Use this when you have an AS number (for example from ipWhoisLookup or ipGeolocation output) and need the operator's name, country, contacts or the IP prefixes it announces. If you only have an IP address, call ipWhoisLookup first to get its ASN. Returns the organisation name and description, country of registration, announced IPv4 and IPv6 prefixes, peering information, admin and technical contacts, and AS sets and blocks. 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": {
      "asn": "<asn>"
    },
    "name": "asnWhoisLookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
asnYesAutonomous System Number to look up. Accepts 'AS15169' or plain '15169'.
formatNoResponse format. Default: json

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent, but the description adds substantial context beyond them: one request to the WhoisFreaks API, authentication via the WHOISFREAKS_API_KEY environment variable or a per-request key on the hosted server, and that the call consumes that account's API credits. It also enumerates concrete failure modes with HTTP codes (401 key invalid, 403 unsupported extension, 404 no data, 429 rate limit) and notes a short message is returned instead of data, which an agent cannot infer from the annotations.

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?

Well front-loaded: purpose first, then routing guidance, then return contents, then behavior and errors. The failure-mode sentence is dense but every element (credits, key source, HTTP codes) is operationally useful; only the enumerated error list is slightly verbose.

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?

For a two-parameter read tool with no output schema, the description covers everything an agent needs: what it returns (org name, country, IPv4/IPv6 prefixes, peering, contacts, AS sets), how it authenticates, that it spends credits, and how failures surface. Nothing material is left to inference.

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 (asn with its 'AS15169' or '15169' forms, and format with a json/xml enum) are already fully documented. The description adds only light context about where ASN values typically come from and nothing about the format parameter, so it sits at the baseline.

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 ('Get the registry WHOIS record for an autonomous system') and immediately clarifies the concept as 'the network operator behind a set of IP routes'. It is clearly distinguishable from the sibling ipWhoisLookup, which works from an IP address rather than an ASN.

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?

Explicitly says when to use it (you have an AS number, e.g. from ipWhoisLookup or ipGeolocation output) and gives the routing rule for the other case: 'If you only have an IP address, call ipWhoisLookup first to get its ASN.' That is a clear when/when-not plus a named alternative.

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