Skip to main content
Glama

Reverse-resolve an IP

arkime_reverse_dns
Read-only

Resolve any IPv4/IPv6 address to its current PTR hostname using Arkime's resolver. Identify external hosts in network traffic with live DNS names, complementing captured session data.

Instructions

Resolve one IP address to its PTR hostname, using Arkime's resolver.

    Use this to put a name on an external address a session talked to —
    `idf-rtr.example.com` says more than `198.51.100.1`. For internal
    assets, malcolm_netbox_lookup gives a far richer answer than a PTR
    record.

    This is a live outbound PTR query leaving the Malcolm deployment now,
    not a read of the capture: measured on Malcolm v26.07.1 it answered
    `dns.google` for 8.8.8.8, a name appearing nowhere in the 58,144
    sessions this capture holds for that address. So it reports DNS today
    rather than the traffic, and resolving an address an adversary controls
    can signal your interest to them. For the names the capture itself
    observed, search event.dataset=dns with malcolm_search instead. Return
    fields, and what resolved:false means, are in the output schema.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYesOne IPv4 or IPv6 address to reverse-resolve, e.g. "8.8.8.8". Not a hostname, not a CIDR range.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond the annotations (readOnlyHint, openWorldHint), the description adds critical behavioral context: it is a live outbound PTR query, not a read of captured data, and may signal interest to adversarial controllers. It also cites a concrete example with a version number, enhancing transparency without contradicting annotations.

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?

Every sentence in the description serves a purpose: it states the operation, provides usage context, warns about outbound behavior, gives a measured example, and points to the output schema for details. Despite being longer than average, it is well-structured, front-loaded, and free of redundant filler.

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

Completeness5/5

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

Given the tool's one parameter, clear annotations, and presence of an output schema, the description is fully complete. It explains the live nature, the meaning of results (via output schema pointer), and contextualizes when this tool is appropriate, leaving no significant gaps for the agent.

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 coverage is 100% with a detailed description in the schema itself ('One IPv4 or IPv6 address... Not a hostname, not a CIDR range'). The main description reinforces 'one IP address' but does not add substantive new meaning beyond the schema, so a baseline score of 3 is appropriate.

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?

The description clearly states the specific action: 'Resolve one IP address to its PTR hostname, using Arkime's resolver.' It distinguishes itself from siblings by explicitly contrasting with malcolm_netbox_lookup and malcolm_search, making the tool's unique scope evident.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus alternatives: use for external addresses, avoid for internal assets (favor malcolm_netbox_lookup), and use malcolm_search for names observed in capture. This directly addresses when/when-not and names alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nagameTW/mcp-server-malcolm'

If you have feedback or need assistance with the MCP directory API, please join our Discord server