Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Get extracted files of a report

get_extracted_files
Read-only

List the files Aether extracted from a report sample, including names, hashes, types, origins, parents, and tags, so you can see what the sample embeds or dropped.

Instructions

The files Aether extracted from one report's file: name, SHA-256, type, origin, parent, whether Aether flags it as interesting, and tags. No per-file verdict: use lookup_hash.

When to use: When the user asks what a sample embeds or dropped.

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_extracted_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
sha256YesSHA-256 of the report's file.
report_idYesAether report ID.
only_interestingNoOnly files Aether flags as interesting, with a count of the others. False to list all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/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 adds real value by describing the shape of what comes back and by noting the tool deliberately omits per-file verdicts. It does not cover pagination or limits on the returned file list, which is the main remaining behavioral gap for a read of this kind.

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 tight sentences with no filler, and the field enumeration is front-loaded before the alternative and the when-to-use line. The long comma-separated field list is dense but each item is informative.

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?

With no output schema, the description compensates by naming the fields returned, and it flags the one thing an agent would otherwise misuse the tool for (per-file verdicts). Nothing essential for correct selection or invocation is missing.

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%, so report_id, sha256, and only_interesting are already documented, including the default of true and the fact that uninteresting files are summarized as a count. The description adds little beyond that and never names the only_interesting switch, so the baseline 3 applies.

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?

States a specific verb and resource (files Aether extracted from one report's file) and enumerates the returned fields: name, SHA-256, type, origin, parent, interesting flag, tags. This makes it clearly distinguishable from lookup_hash, which the description explicitly names as the tool that carries per-file verdicts.

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?

Provides an explicit 'When to use' condition ('the user asks what a sample embeds or dropped') and an explicit exclusion plus redirect ('No per-file verdict: use lookup_hash'). An agent can route between this tool and lookup_hash without opening either schema.

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