Skip to main content
Glama
dadepo

WHOIS MCP Server

by dadepo

arin_expand_as_set

Expand ARIN-managed AS-SET objects into concrete ASN numbers for network analysis, route filtering, and policy generation with configurable recursion depth.

Instructions

Efficiently expand AS-SET objects from the ARIN IRR database into concrete ASNs with configurable depth. This tool is specifically for the ARIN RIR (North America region - United States, Canada, parts of Caribbean). Use this instead of whois_query when you need ASNs from an ARIN AS-SET. CRITICAL: For 'top-level', 'direct', or 'immediate' members, use max_depth=1. For complete expansion, use max_depth=10+. Large AS-SETs may have nested structures - choose depth carefully to balance completeness vs speed. Automatically handles recursive expansion, deduplication, and cycle detection. Perfect for network analysis, route filtering, and policy generation for ARIN-managed AS-SETs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
setnameYesAS-SET name to recursively expand into concrete ASN numbers from ARIN IRR database. Examples: 'AS-COMCAST', 'AS-VERIZON', 'AS-ATT'. The tool will automatically resolve all nested AS-SETs and return a complete list of individual ASNs contained within the hierarchy from ARIN IRR records.
max_depthNoMaximum recursion depth for AS-SET expansion (1-20 levels, default: 10). IMPORTANT: Use depth=1 for 'top-level' or 'direct' members only. Use depth=2-3 for shallow analysis, depth=10 for complete expansion. Higher values provide more complete results but take much longer to process. For questions about 'immediate' or 'direct' members, always use depth=1.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: automatic handling of recursive expansion, deduplication, and cycle detection; performance implications (higher depth takes longer); and practical applications (network analysis, route filtering, policy generation). This provides comprehensive behavioral context beyond basic functionality.

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 description is appropriately sized and front-loaded with the core purpose. Every sentence adds value: purpose statement, regional specificity, sibling tool differentiation, depth guidance, behavioral traits, and use cases. While slightly dense, it avoids redundancy and maintains focus on essential information.

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?

Given the tool's complexity (recursive expansion with configurable depth), no annotations, and the presence of an output schema, the description provides excellent contextual completeness. It covers purpose, usage guidelines, behavioral traits, parameter semantics, and practical applications, making it fully understandable without relying on structured fields.

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?

With 100% schema description coverage, the baseline is 3. The description adds significant value by explaining the practical implications of max_depth choices with specific examples (depth=1 for top-level, depth=10+ for complete expansion) and warnings about performance trade-offs. However, it doesn't add meaningful semantic context for the setname parameter beyond what's in 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 purpose: 'Efficiently expand AS-SET objects from the ARIN IRR database into concrete ASNs with configurable depth.' It specifies the verb (expand), resource (AS-SET objects), and distinguishes it from sibling tools by mentioning ARIN RIR region and contrasting with whois_query for ASN extraction from AS-SETs.

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?

The description provides explicit guidance on when to use this tool: 'Use this instead of whois_query when you need ASNs from an ARIN AS-SET.' It also offers detailed depth recommendations for different scenarios (e.g., max_depth=1 for top-level members, max_depth=10+ for complete expansion) and warns about balancing completeness vs speed for large AS-SETs.

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/dadepo/whois-mcp'

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