Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

Get MITRE techniques

get_mitre_techniques
Read-only

Retrieves MITRE ATT&CK tactics and techniques mapped to an Aether report, with the signal groups behind each, so you can explain what a sample does in ATT&CK terms.

Instructions

The MITRE ATT&CK tactics and techniques Aether mapped in one report, from the signal groups that explain its verdict, with the signal groups behind each technique.

When to use: When the user asks what a sample does in ATT&CK terms (techniques, tactics, TTPs).

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

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?

readOnlyHint=true already declares the safety profile, and the description adds genuinely new behavioral content: the result is a per-report mapping of tactics/techniques and includes the signal groups that explain the verdict and back each technique. That previews the return shape usefully in the absence of an output schema; it only omits failure cases (missing report, unmapped sample).

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 the deliverable front-loaded and usage second; nothing is redundant. The first sentence is mildly convoluted ('from the signal groups that explain its verdict, with the signal groups behind each technique' repeats 'signal groups'), costing a little clarity.

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 a read-only, two-required-parameter report lookup with no output schema, the description covers what is returned and when to call it. Only the error/empty-mapping behavior is unaddressed, which is a minor gap at this complexity.

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%, and both required parameters (report_id, sha256) carry their own descriptions and patterns. The tool description adds no further meaning about how the two identifiers relate or whether sha256 must match the report's file, so the schema does all the work — baseline 3.

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?

States a specific verb+resource: returns the MITRE ATT&CK tactics and techniques Aether mapped for one report, plus the signal groups behind each. The purpose is unambiguous, but it never names a sibling (e.g. resolve_technique) that could be confused with a per-report technique listing.

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 ties the tool to the user asking what a sample does in ATT&CK terms (techniques, tactics, TTPs). It gives no exclusions or alternative routes for the same intent, but the positive guidance is clear enough to select the tool.

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