Skip to main content
Glama
aether-mcp

aether-mcp

Official
by filescanio

List MITRE ATT&CK techniques

resolve_technique
Read-only

Map keywords or synonyms to MITRE ATT&CK technique IDs and names so you can identify the exact technique ID before searching by technique.

Instructions

Get the MITRE ATT&CK technique IDs and names Aether maps to, matching a query.

When to use: Before searching by technique, to get its exact ID.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resolve_technique"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoKeywords for the technique ID or name, with synonyms (any matches), e.g. ['injection', 'hollowing']. Omit for all (large).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds context beyond that: it discloses the return content (technique IDs and names) and the scope limit that only techniques Aether maps to are returned, which prevents an agent from expecting the full ATT&CK catalog. It says nothing about result size limits or pagination, a minor residual gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler. The purpose is front-loaded and the usage condition follows immediately, so an agent can parse both in one pass.

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 single optional-parameter read tool with no output schema, the definition covers purpose, trigger, return content, and scope. The main omission is the relationship to the sibling get_mitre_techniques, which matters for routing in this crowded tool set.

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 the single 'query' parameter is already documented with synonym/any-match semantics and omit-for-all behavior. The description only echoes 'matching a query' without adding format or matching-rule detail beyond the schema. Baseline 3 is appropriate.

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 and resource: 'Get the MITRE ATT&CK technique IDs and names Aether maps to, matching a query.' The scoping phrase 'Aether maps to' narrows the resource meaningfully. It does not, however, distinguish itself from the sibling get_mitre_techniques, so an agent cannot tell from the text alone which of the two to pick.

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?

Explicit 'When to use' line places the tool in a workflow: resolve a name/keyword to an exact ID before searching by technique. That is a clear positive trigger. No negative guidance is given (e.g., when to skip resolution and search directly), which keeps it below a 5.

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