Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Get IOCs of a report

get_iocs
Read-only

Retrieve indicators of compromise extracted from a report, optionally filtered by IOC type, with the location where each was found. Use it to collect IOCs for a sample found via search or lookup.

Instructions

The indicators of compromise Aether extracted from one report, including those found in extracted files, by type, with where each was found.

When to use: To collect the IOCs of a sample found with search or a lookup.

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": {
      "report_id": "<report_id>",
      "sha256": "<sha256>"
    },
    "name": "get_iocs"
  }
}

Input Schema

NameRequiredDescriptionDefault
typesNoOnly these IOC types. Omit for all.
sha256YesSHA-256 of the report's file.
report_idYesAether report ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, so the description only needs to add data-shape context — and it does: results are per-type and include where each IOC was found, plus coverage of IOCs inside extracted files. It omits any note on result volume, truncation, or whether an empty set is possible, which is the main remaining gap for a tool with no output schema.

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?

Two sentences, no filler, with the output content stated before the usage rule. The first sentence is a noun-phrase fragment rather than a verb-led statement, which is slightly less scannable but not wasteful.

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 only three parameters, full schema coverage, and a readOnly annotation, the description supplies what an agent needs: what is returned, at what granularity, and which upstream call produces the identifiers. Only return-volume behavior and explicit sibling routing are left implicit.

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 description coverage is 100%, so types, sha256, and report_id are all documented in the schema itself. The description adds no extra semantics such as how types interacts with the report scope or why both sha256 and report_id are required together; baseline 3 applies.

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 resource and scope: IOCs Aether extracted from a single report, including those pulled from extracted files, grouped by type with provenance. It is clearly distinguishable from the lookup_*/pivot_ioc family, though it does not explicitly name a sibling the way a top-tier definition would.

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?

"When to use: To collect the IOCs of a sample found with search or a lookup" gives a concrete entry condition and names the upstream tools that produce the report_id/sha256. It stops short of stating when NOT to use it (e.g. cross-report pivoting via pivot_ioc or prevalence via get_ioc_prevalence).

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