Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_groups_by_alias

Retrieve MITRE ATT&CK threat groups (intrusion sets) that match a given alias, such as 'Cozy Bear' or 'NOBELIUM', with optional descriptions and domain filtering.

Instructions

Get APT groups (intrusion sets) matching a given alias.

Many groups have multiple aliases—e.g., APT29 is also known as:
"Cozy Bear", "NOBELIUM", "Midnight Blizzard", etc.

This tool returns all groups whose alias list contains the given alias
(case-insensitive exact match, per MITRE's own alias indexing).

Args:
    alias: Alias to search for (e.g., "Cozy Bear", "NOBELIUM").
    domain: ATT&CK domain ("enterprise", "mobile", "ics").
    include_description: Whether to include group descriptions.

Returns:
    {
      "count": <number>,
      "groups": [
        {
          "attack_id": "GXXXX",
          "name": "<group name>",
          "aliases": [...],
          "stix_id": "<intrusion-set--UUID>",
          "description": "<text or null>"
        },
        ...
      ],
      "formatted": "<formatted list>",
      "message": "<status summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aliasYes
domainNoenterprise
include_descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description bears full burden. It discloses the case-insensitive exact match behavior, return structure, and alias concept. It does not mention side effects or limitations, but as a read-only query, this is sufficient.

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 description is well-structured with examples and Args/Returns sections, but it is slightly verbose. The purpose is front-loaded, and every part adds value.

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?

Given the tool complexity (alias matching, multiple groups, optional parameters), the description fully documents input, behavior, and return structure. The output schema is described in text, providing complete context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description provides detailed parameter explanations, including alias examples, domain enumeration, and include_description default. It adds significant value beyond the schema.

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?

The description clearly states it retrieves APT groups by alias, provides examples, and distinguishes from siblings like get_group_by_name and search_groups by focusing on alias matching.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool does but does not explicitly state when to use it versus alternatives or when not to use it. It implies usage context through examples but lacks direct guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/imouiche/complete-mitre-attack-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server