Skip to main content
Glama
Sign In
MITRE ATT&CK MCP Server

MITRE ATT&CK MCP Server

by imouiche
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_groups

Search MITRE ATT&CK intrusion sets (APT groups) by name, alias, or description across enterprise, mobile, or ICS domains.

Instructions

Search MITRE ATT&CK intrusion sets (APT groups) by name, alias, or
description (case-insensitive).

If the query is empty, all groups in the domain are returned.

Args:
    query: Search keyword (name, alias, or any text in the description).
    domain: ATT&CK domain ("enterprise", "mobile", "ics").
    include_description: Whether to include descriptions in the output.

Returns:
    {
      "count": <number of matches>,
      "groups": [
        {
          "attack_id": "GXXXX",
          "name": "...",
          "aliases": [...],
          "stix_id": "...",
          "description": "..." | null
        },
        ...
      ],
      "formatted": "<LLM-friendly block>",
      "message": "<summary>"
    }

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": "search_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
domainNoenterprise
include_descriptionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It transparently explains search behavior, parameter effects, and return format. It does not mention any destructive side effects (none expected) or authentication needs, but is sufficient for a read-only search tool.

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?

Description is well-structured with a clear purpose sentence and an 'Args' section. It is front-loaded and concise, with every sentence adding necessary information. No redundant wording.

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?

The description includes a detailed output schema, covering all return fields. It specifies behavior for empty queries and case-insensitivity. Given the output schema in the description, the agent has complete information to use the tool correctly.

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 description adds full meaning for each parameter: query (search keyword), domain (ATT&CK domain), include_description (toggle). Default values and types are explained, providing essential context 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 it searches MITRE ATT&CK intrusion sets by name, alias, or description, case-insensitive. It distinguishes itself from siblings like 'get_all_groups' (returns all) and 'get_group_by_name' (exact match) by specifying search functionality.

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 implies usage for searching, but lacks explicit guidance on when to use this tool versus alternatives like 'get_group_by_name' or 'get_all_groups'. No mention of when not to use it or prerequisites.

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

Deploy Server

Other Tools