Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Get threat attribution of a report

get_threat_attribution
Read-only

Retrieves malware family attribution for each file in a report, including family, type, score, description, and supporting evidence to explain why a sample was attributed.

Instructions

The malware families Aether attributed to each file of one report (input, extracted and downloaded files): family, type, score (0-100), description and the evidences behind it. The highest score is the strongest attribution and takes precedence over weak ones. An MWCFG evidence means a malware config was extracted: see it with get_malware_config. Empty if nothing was attributed.

When to use: When the user asks which family a sample is, or why it was attributed to it.

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

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
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered and the description is not burdened there. It does add genuinely useful behavior: the score semantics (highest takes precedence over weak ones) and the meaning of an empty result. It does not describe response shape beyond field naming, pagination, or what an evidence object looks like.

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?

Front-loaded with the payload and return fields, then a short cross-reference and a 'When to use' line. Mostly earns its words, though the field enumeration in the first sentence is slightly padded relative to the remaining content.

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 carries the return-value burden and does so by naming the returned fields and the empty-case behavior. For a two-parameter read-only lookup it is close to complete; only the relationship between report_id and sha256 (both required) goes unstated.

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 both required parameters (report_id and sha256) are already documented in the schema, which sets the baseline at 3. The description clarifies scope, that results are per file within one report including input, extracted and downloaded files, but adds no per-parameter syntax or constraint detail.

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: the malware families attributed to each file of one report, and enumerates returned fields (family, type, score, description, evidences). It also differentiates itself from get_malware_config by naming the exact condition (an MWCFG evidence) that routes the agent to that sibling.

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' clause covers the primary intent: asking which family a sample is, or why it was attributed. A conditional hand-off to get_malware_config is also given. It lacks an explicit when-not or statement about how it relates to siblings like resolve_family, but the positive guidance is clear.

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