Skip to main content
Glama

ip_intel

Retrieve full IP profiles with geolocation, ASN, organization, open ports, hostnames and CVEs. Uses keyless APIs with a fallback source to support reconnaissance investigations.

Instructions

Full IP profile: geolocation/ASN/org + Shodan InternetDB open ports, hostnames, CVEs.

Uses keyless APIs (ip-api.com + internetdb.shodan.io) with an ipinfo.io fallback.

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

Input Schema

NameRequiredDescriptionDefault
ipYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that the lookups are keyless and names the three upstream providers (ip-api.com, internetdb.shodan.io, ipinfo.io fallback), which is genuine behavioral context. It leaves out rate limits, timeout/failure behavior, and whether results merge or fail over between providers.

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 short lines, front-loaded with what the tool returns and followed by the data-source/fallback detail. Every sentence adds information, and there is no filler or redundant restatement of the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter lookup with no output schema, the description covers the source stack and the returned fields reasonably well. It still omits accepted input formats and what happens on partial provider failure, which matter for correct invocation of a multi-source enrichment tool.

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?

Only one parameter exists, and the schema coverage is 0%, so the description must supply format semantics. It implies the parameter is an IP address but never says whether IPv4, IPv6, CIDR ranges, or hostnames are accepted, which leaves an agent guessing at input validity.

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 clear resource (IP address) and enumerates the returned data: geolocation, ASN, org, Shodan InternetDB open ports, hostnames, and CVEs. It tells the agent this is a broad profile tool, but doesn't explicitly distinguish itself from overlapping siblings like recon_ip, ip_whois, greynoise_ip, or asn_lookup.

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 by the phrase 'Full IP profile,' which suggests a comprehensive lookup rather than a narrow one. There is no when-to-use guidance, no exclusions, and no naming of alternatives such as cve_intel or ip_whois that could cover narrower needs.

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