Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Look up IP addresses

lookup_ip
Read-only

Checks the reputation of up to 100 IPv4 addresses in one call, returning verdicts, MD Cloud detections, and recent sandbox reports for files tied to each address.

Instructions

Aether's reputation for up to 100 IP addresses in one call: per IP, verdict (may reflect the files that contain it), MD Cloud detections and a few recent sandbox reports of files that contain it (report_id, flow_id). More: pivot_ioc.

When to use: To check IP addresses.

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": {
      "ips": "<ips>"
    },
    "name": "lookup_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipsYesIPv4 addresses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real value by disclosing the batch ceiling and the shape of each result, including the caveat that verdict "may reflect the files that contain it." It omits behavior on invalid/non-IPv4 input, partial failures, and whether results are cached or rate-limited, which matters for a 100-item batch call.

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?

Return-value information is front-loaded and dense with specifics (verdict, MD Cloud, report_id, flow_id). The trailing "When to use" line and the fragment "More: pivot_ioc" are weak but not verbose; nothing is badly padded.

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, the description carries the burden of describing results and does so adequately, listing the three result components and the verdict caveat. Only error/batching edge-case behavior is missing, which is a modest gap for a one-parameter read 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?

Schema coverage is 100% and the single parameter is already documented as IPv4 addresses with minItems 1 and maxItems 100. The description's "up to 100 IP addresses in one call" largely duplicates the schema constraints rather than adding format, ordering, or partial-result semantics.

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?

States a specific verb+resource: reputation lookup for up to 100 IP addresses in a single call, and enumerates what comes back per IP (verdict, MD Cloud detections, sandbox report_id/flow_id). The resource (IP addresses) distinguishes it from lookup_domain/lookup_url/lookup_hash siblings, though it never names those alternatives explicitly.

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

Usage Guidelines2/5

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

"When to use: To check IP addresses." simply restates the tool's purpose rather than giving conditions, prerequisites, or exclusions. The only routing hint is the terse "More: pivot_ioc", which gives no criterion for when pivoting is preferable to a plain reputation lookup.

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