Skip to main content
Glama

Network Info

network_info
Read-onlyIdempotent

"What ASN does IP [X] belong to" / "network info for [IP]" / "what prefix is [IP] in", get the allocated prefix and originating ASN for an IPv4/IPv6 address. Use for "which network owns this IP", DDoS source attribution, hosting-provider lookup.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resource": "8.8.8.8"
    },
    "name": "network_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceYesIPv4/IPv6 address

Output Schema

NameRequiredDescriptionDefault
dataNoNetwork info including allocated prefix and ASN
statusNoAPI response status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "resource": "8.8.8.8"
      +  },
      +  {
      +    "resource": "2001:4860:4860::8888"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "data": {
      +      "description": "Network info including allocated prefix and ASN",
      +      "type": "object"
      +    },
      +    "status": {
      +      "description": "API response status",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the query forms and the fact that the result includes the allocated prefix and originating ASN, but it does not disclose deeper behavior such as data source, freshness, or coverage limits. With annotations carrying the main behavioral burden, this is adequate but not rich.

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 short and front-loads the core operation before listing query phrasings and use cases. The quoted user-query forms are slightly unconventional but serve retrieval matching. It is not bloated, though the quoted alternatives could be tightened.

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?

For a simple one-parameter, read-only lookup with an output schema and rich annotations, the description covers purpose, input type, and intended use cases. The only meaningful omission is explicit sibling differentiation. Nothing essential for correct invocation is missing.

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%, and the single resource parameter is already documented as an IPv4/IPv6 address with examples. The description mentions IPv4/IPv6 addresses but does not add format rules, validation behavior, or special cases beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: get the allocated prefix and originating ASN for an IPv4/IPv6 address. That is clear enough for an agent to understand the operation without opening the schema. It does not explicitly distinguish itself from closely related siblings such as as_overview or prefix_overview, so it falls short of a 5.

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?

It provides concrete usage contexts: 'which network owns this IP', DDoS source attribution, and hosting-provider lookup. This tells an agent when the tool is appropriate. However, it gives no explicit exclusions or alternative-tool routing, such as when to use as_overview or prefix_overview instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.