Skip to main content
Glama

reverse_ip

Identify other domains hosted on the same IP address to map shared infrastructure and support authorized OSINT investigations.

Instructions

Reverse-IP lookup: other domains hosted on the same IP (Hackertarget, keyless).

Rate limited upstream (a few dozen/day); a failure usually means quota, not that the IP hosts nothing.

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

Input Schema

NameRequiredDescriptionDefault
ipYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the upstream provider (Hackertarget), that no API key is needed, the rough rate limit (a few dozen/day), and — importantly — that a failure usually means quota exhaustion rather than an empty result. That last point prevents a serious misinterpretation of an empty/error response.

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?

Front-loaded with the definition, then two short sentences of operational caveats. Nearly every sentence earns its place; the parenthetical '(Hackertarget, keyless)' is tersely useful rather than filler.

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 single-parameter, read-only lookup with no output schema, the description covers purpose, provider, rate limits, and error interpretation — the main things an agent needs. The remaining gap is input format expectations, which matter for a network-address 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 ('ip'), and the schema provides zero description coverage, so the description should compensate but only implies the input type through context. It adds no guidance on accepted formats (IPv4 vs IPv6, single vs multiple), leaving an ambiguity the schema does not resolve.

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?

Names a specific verb+resource ('Reverse-IP lookup') and clarifies the output is 'other domains hosted on the same IP', which separates it conceptually from a plain reverse_dns or IP-intel lookup. It does not explicitly contrast itself with any named sibling, 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 Guidelines3/5

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

Usage is implied rather than stated: an agent learns this is for domains sharing an IP, and that failures are likely quota-related. No explicit when-to-use or when-not-to-use versus reverse_dns, ip_intel, or greynoise_ip is given.

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