Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Look up domains

lookup_domain
Read-only

Check reputation for up to 100 domains in one call, returning per-domain verdicts, MD Cloud detections, and recent sandbox reports for files containing each domain.

Instructions

Aether's reputation for up to 100 domains in one call: per domain, 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 domains.

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": {
      "domains": "<domains>"
    },
    "name": "lookup_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesDomain names, e.g. ['example.com'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description goes further by disclosing that at most 100 domains are accepted per call, that the verdict 'may reflect the files that contain it' (an important interpretive caveat), and that results include MD Cloud detections plus a limited set of recent sandbox reports. These are behavioral traits beyond what the schema or annotations convey. It does not address rate limits, unknown-domain handling, or whether results are cached/stale.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first paragraph is dense and front-loaded with the useful content about outputs and the verdict caveat. However, the second line ('When to use: To check domains.') consumes space without earning it, and the trailing 'More: pivot_ioc.' is an unexplained fragment. Roughly a quarter of the text is waste.

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 usefully enumerates the returned fields and warns about the verdict's file-based nature, so an agent can interpret results without extra documentation. Gaps remain on what happens with unknown or invalid domains and on how many sandbox reports constitute 'a few'. For a one-parameter batch lookup this is close to complete.

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?

There is a single parameter and schema description coverage is 100%, with the item type and an example ('example.com') already documented in the schema. The description's mention of the 100-domain cap duplicates maxItems rather than adding meaning. Baseline 3 applies since the schema carries the parameter burden.

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 specific operation on a specific resource: reputation lookup ('Aether's reputation') for a batch of domains, capped at 100 per call, with named output fields (verdict, MD Cloud detections, sandbox report_id/flow_id). That is enough detail to tell it apart from lookup_ip, lookup_url and lookup_hash, which cover other indicator types. It stops short of a 5 only because it never explicitly contrasts itself with those siblings.

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?

The guidance is a single line, 'When to use: To check domains.', which merely restates the tool name and adds no decision information. There is no statement of when not to use it, no prerequisites, and the only pointer to another tool ('More: pivot_ioc.') is a dangling reference with no condition attached. An agent gains no routing signal from this section.

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