Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Get emulation of a report

get_emulation
Read-only

Retrieve emulated file behavior as events—processes, files, registry and HTTP activity—to answer what a sample does when run, including persistence and downloaded files.

Instructions

What each emulated file of one report did, as events: processes, files, registry, HTTP requests and more. Covers the input file, files extracted from it and files it downloaded. Script and payload contents and HTTP response bodies are left out. Empty if nothing was emulated.

When to use: When the user asks what a sample does when run: its behavior, persistence or network activity.

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

Input Schema

NameRequiredDescriptionDefault
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?

Beyond readOnlyHint=true, the description adds real behavioral context: the scope covers the input file, extracted files and downloaded files, script/payload contents and HTTP response bodies are excluded, and the result is empty if nothing was emulated. That is a meaningful disclosure of coverage boundaries; it stops short of describing event shape or volume, but the annotations already cover the safety profile.

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?

The return scope is front-loaded and the usage trigger is separated cleanly, with no filler sentences. The phrase "and more" is slightly vague in an otherwise precise enumeration, which keeps it from a top score.

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?

There is no output schema, but the description explains what the response contains, what it omits, and the empty case — enough for an agent to know what to expect and to set user expectations. It does not indicate result size, ordering or pagination, a minor gap for a tool that can return many events.

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%: both report_id and sha256 carry format patterns and descriptions in the input schema. The description adds nothing about either parameter (e.g. which one drives lookup or whether they must be consistent), so the baseline of 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?

"What each emulated file of one report did, as events: processes, files, registry, HTTP requests and more" names a specific resource (emulation events for a report) and enumerates the event categories returned. It is clearly distinct from siblings like get_extracted_files or get_iocs by focusing on runtime behavior, though it does not explicitly name a sibling it is not.

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?

The "When to use" line gives a concrete trigger: the user asks what a sample does when run — behavior, persistence or network activity. That is clear positive guidance, but there are no exclusions (e.g. when a static scan result would suffice instead) and no named alternatives.

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