Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_all_groups

Retrieve all APT threat groups (intrusion sets) from MITRE ATT&CK by domain. Filter revoked groups and optionally include descriptions for security analysis.

Instructions

Get all APT groups (intrusion sets) in a domain.

Args:
    domain: ATT&CK domain ("enterprise", "mobile", "ics").
    remove_revoked_deprecated: Whether to exclude revoked/deprecated groups.
    include_description: Whether to include descriptions.

Returns:
    {
      "domain": "<domain>",
      "count": <number of groups>,
      "groups": [
        {
          "attack_id": "GXXXX",
          "name": "<group name>",
          "aliases": [...],
          "stix_id": "<intrusion-set--UUID>",
          "description": "<text or null>"
        },
        ...
      ],
      "formatted": "<optional human-readable listing>",
      "message": "<summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
include_descriptionNo
remove_revoked_deprecatedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses behavior: it lists parameters and detailed return structure including fields like attack_id, name, aliases, etc. No hidden side effects mentioned, but it's a read operation.

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 Args and Returns sections, but the return JSON is detailed; could be slightly more concise. However, every part adds value and it's front-loaded with purpose.

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's simplicity and the presence of a complete output schema in the description, all relevant information is covered. Parameters and return values are fully documented.

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's Args section explains each parameter: domain with allowed values, remove_revoked_deprecated and include_description with clear semantics. The description adds full meaning beyond the bare 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 'Get all APT groups (intrusion sets) in a domain,' specifying verb, resource, and scope. It distinguishes from siblings like 'get_groups_by_alias' and 'search_groups' by implying this returns the full set.

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 does not explicitly state when to use this tool versus alternatives. It lists parameters but lacks context like 'use search_groups for specific names.' Usage is implied but not contrasted.

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