Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Pivot: reports that contain an IOC

pivot_ioc
Read-only

Search Aether reports by IP, domain, URL, email, or SHA-256 to find related samples and pivot across campaigns; use date ranges to reach older matches beyond the 200 newest.

Instructions

Search the Aether reports that contain an IP, domain, URL, email or file SHA-256. Only the 200 newest matches are reachable; to go further back, set date_from and date_to to an earlier range.

When to use: To find other samples related to an IOC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pivot_ioc"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNoIPv4 address.
urlNoFull URL.
pageNoPage number (5 files per page, newest report of each).
emailNoEmail address.
domainNoDomain name.
sha256NoSHA-256 of a file, e.g. an extracted or downloaded one.
date_toNoEnd date YYYY-MM-DD.
date_fromNoStart date YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the interesting behavioral detail: results are capped at the 200 newest matches and older data is only reachable by narrowing date_from/date_to. That result-window limit is exactly the kind of constraint an agent needs before calling. Return format is not described, but no output schema exists to rely on either.

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 tight paragraphs: the capability and result-cap caveat are front-loaded, then a short usage line. Every sentence carries information the schema or annotations do not.

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 an 8-parameter, no-output-schema, read-only search tool, the description covers purpose, result limits, historical paging, and use case. It never states that at least one IOC identifier should be supplied (zero required params), which is the one invocation rule left ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are already documented; the description's added value is explaining the date_from/date_to interplay with the 200-result cap, which the schema alone does not convey. It also enumerates the supported IOC types, aligning with ip/url/email/domain/sha256.

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 gives a specific verb and resource ('Search the Aether reports that contain an IP, domain, URL, email or file SHA-256') and the title frames it as a pivot operation. It stops short of naming how it differs from siblings such as lookup_ip or lookup_domain, which likely return IOC details rather than related reports.

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?

An explicit 'When to use' line ties the tool to a concrete goal: finding other samples related to an IOC. There are no exclusions or named alternatives (e.g., when to prefer lookup_hash or find_similar), so the agent must infer the boundary itself.

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