Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_group_by_name

Find an APT group by searching its name or alias with case-insensitive partial matching, returning group details and optional description.

Instructions

Retrieve an intrusion set (APT group) by name or alias (case-insensitive match).

This tool searches ATT&CK intrusion sets by name or alias and returns the first
matching group. Matching is case-insensitive and supports partial matches.

Examples:
    - get_group_by_name("APT29")
    - get_group_by_name("Lazarus")
    - get_group_by_name("Fancy Bear")

Args:
    group_name: The group name or alias to search for (case-insensitive).
    domain: ATT&CK domain ("enterprise", "mobile", "ics").
    include_description: Whether to include descriptions in the output.

Returns:
    {
      "found": bool,
      "group": {
          "attack_id": "<GXXXX>",
          "name": "<group name>",
          "aliases": [...],
          "stix_id": "<intrusion-set--...>",
          "description": "<description or null>"
      },
      "formatted": "<human-readable text>",
      "message": "<status>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
group_nameYes
include_descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Despite no annotations, the description fully discloses behavior: returns first matching group, case-insensitive, partial matches, and details the return schema including 'found' and 'message' fields.

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, but slightly verbose with repeated mention of 'case-insensitive'. Still efficient and 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 output schema is fully documented in the description and the tool is simple, the description covers all aspects: purpose, parameters, behavior, return format, and example usage.

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 coverage is 0%, but the description adds meaning for all three parameters: group_name (case-insensitive search), domain (ATT&CK domain with default), include_description (controls output). This fully compensates for missing schema descriptions.

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 the verb 'retrieve' and resource 'intrusion set (APT group)' by name or alias, distinguishing it from siblings like get_all_groups (returns all groups) and search_groups (broader search).

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?

The description explains when to use (search by name/alias with case-insensitive partial matching) and includes examples, but does not explicitly say when not to use or compare with alternatives like get_groups_by_alias.

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