Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

network_asn_lookup

Identify the Autonomous System (ASN) owning or routing an IP address, domain, or AS number, providing organization, country, and registry.

Instructions

ASN Lookup. Resolve an IP address, domain name, or AS number to its Autonomous System (ASN number, owning organization, country, RIR registry) by making an outbound query to an external ASN/geolocation data source (ip-api.com), optionally via a registered remote worker peer. Makes a live network call, so results depend on third-party data and are not deterministic. Use this to identify who owns/routes an IP. Use network_whois for domain/IP registration and contact records, network_bgp_route_lookup for AS-PATH and prefix routing analysis, and network_ip_geolocation for detailed geographic/ISP data. Anonymous limit 15/min, 90/hour, 300/day (authenticated 30/180/600); CAPTCHA after 30 requests/hour. Returns the resolved IP, an asn object, and the data source; geolocation only when requested (prefixes and upstreams are not populated by the default ip-api.com source).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesIP address, domain name, or AS number to look up, for example 8.8.8.8, google.com, or AS15169.
includeGeolocationNoWhen true, include a geolocation object (country, region, city, zip, timezone, coordinates).
includePrefixesNoWhen true, request announced prefixes (not populated by the default ip-api.com source; needs a BGP data source/worker).
includeUpstreamsNoWhen true, request upstream AS peers (not populated by the default ip-api.com source; needs a BGP data source/worker).
worker_idNoOptional registered healthy worker peer ID. Omit to use the default master-server behavior.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the lookup completed.
targetNoThe input target, echoed back.
resolvedIpNoIP the target resolved to (null for direct AS-number input).
asnNoAutonomous System details, or null when none found.
geolocationNoPresent only when includeGeolocation is true; null otherwise.
prefixesNoAnnounced prefixes when includePrefixes is true (empty from the default source); null otherwise.
upstreamsNoUpstream AS peers when includeUpstreams is true (empty from the default source); null otherwise.
dataSourceNoOrigin of the data, e.g. ip-api.com, Direct ASN input, or Private/Reserved IP.
timestampNoISO-8601 response time.
Behavior5/5

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

Beyond annotations, it details live network call, third-party dependency, non-determinism, rate limits, and limitations of optional parameters (prefixes/upstreams).

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?

Single paragraph with front-loaded purpose and key details; each sentence adds value without redundancy.

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?

Covers purpose, behavior, alternatives, parameters, rate limits, return content, and limitations; complete for a lookup tool with 5 parameters.

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 covers all parameters with descriptions; description adds value by explaining behavior of boolean flags and worker_id, though schema coverage is already high.

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 resolves IP/domain/AS to ASN details, and explicitly names sibling tools for differentiation, making it highly specific and unambiguous.

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 explicitly states when to use this tool ('identify who owns/routes an IP') and provides alternative tools for different purposes (whois, BGP, geolocation).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server