Skip to main content
Glama

recon_ip

Performs one-shot IP reconnaissance by combining geolocation/ASN, Shodan InternetDB, PTR, reverse-IP domains, and top-20 ports in parallel to map a host.

Instructions

One-shot IP recon: geo/ASN, Shodan InternetDB, PTR, reverse-IP domains, top-20 ports.

Combines 5 keyless sources in parallel. Follow up with a wider port_scan or certificate lookups on discovered hostnames.

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

Input Schema

NameRequiredDescriptionDefault
ipYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful traits: five keyless sources (no credentials required), parallel execution, and a hard cap of top-20 ports that tells the agent results will be partial. It omits rate limiting, latency/retry behavior, and whether results are cached, which matters for a fan-out tool hitting five upstream sources.

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 sentences, both carrying load: the first defines scope, the second defines escalation. No filler, no restatement of the tool name, and the source list is front-loaded before the follow-up advice.

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?

There is no output schema, and the description compensates by enumerating the returned sections, so an agent knows roughly what comes back. Combined with disclosed keyless/no-auth behavior and the port cap, the definition is sufficient to call correctly, though it does not say how the sections are structured or what a failed source does to the response.

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?

The single parameter is undocumented at 0% schema coverage — the schema only says "ip". The description implies a single address rather than a range or CIDR, but never states IPv4 vs IPv6 support or accepted formats, so the agent must guess on input shape.

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?

Names a specific verb+resource ("IP recon") and enumerates exactly which sources feed it: geo/ASN, Shodan InternetDB, PTR, reverse-IP domains, top-20 ports. The word "one-shot" plus the bounded "top-20 ports" scope separates it from a fuller scan and from the domain-oriented siblings without opening any schema.

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?

Gives a clear usage context (single-shot enrichment of one IP) and an explicit follow-up path: escalate to a wider port_scan or certificate lookups on hosts discovered from reverse-IP domains. It does not say when to prefer ip_intel, greynoise_ip, or recon_deep over this tool, so the alternatives side of the guidance is incomplete.

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