Skip to main content
Glama

Look up an IP

lookup_prefix

Resolve a single IPv4 address to ASN, organization, cloud-published region, RDAP registration, and PeeringDB facilities, prioritizing provider-published regions over geoIP guesses.

Instructions

Identify a single address: ASN and org, the cloud's own published region for the prefix, RDAP registration, and PeeringDB facilities. The published cloud region outranks any geoIP database.

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": "lookup_prefix"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesIPv4 address.
include_facilitiesNoInclude PeeringDB facilities (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the whole disclosure burden. It reveals the data sources it consults (RDAP, PeeringDB) and a precedence rule for cloud region vs geoIP, which is genuinely useful, but it omits whether these are external network calls, likely latency, authentication, rate limits, or what happens for an unregistered or bogon prefix.

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?

Two tight sentences with the resource scope front-loaded and the result components following. Every clause carries information: the returned fields and the authority ordering between cloud region and geoIP. No filler or redundancy.

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?

With no output schema and no annotations, the description usefully enumerates the returned data components, which is the main thing an agent needs to judge fit. The remaining gap is operational behavior for the external lookups (latency, partial results, unknown prefixes), which matters for a network-lookup tool but is only partially implied.

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 the schema already defines both 'ip' (IPv4 address) and 'include_facilities' (default true). The description mentions PeeringDB facilities as part of output but never references the toggle that controls them, so it adds no meaning beyond the schema. Baseline 3 applies.

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 verb 'identify' plus the resource 'a single address' is specific, and the description enumerates exactly what is returned (ASN/org, published cloud region, RDAP registration, PeeringDB facilities). It scopes the tool to one address at a time, which implicitly separates it from any bulk or probe-style sibling. It never names or contrasts a sibling tool, so it stops short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied through the phrase 'single address', and the sentence 'The published cloud region outranks any geoIP database' is a useful decision rule for interpreting results. There is no explicit statement of when to choose this over alternatives like locate_model or trace_endpoint, and no when-not guidance or prerequisites.

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