Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_campaigns_attributed_to_group

Retrieve all campaigns attributed to a specific APT group by its STIX ID, with optional domain filtering and descriptions for enterprise, mobile, or ICS.

Instructions

Get all campaigns attributed to a specific intrusion set (APT group),
identified by its STIX ID.

Campaigns represent specific operations or intrusion events attributed
to a threat group.

Args:
    group_stix_id: STIX UUID of the group (e.g., "intrusion-set--UUID").
    domain: ATT&CK domain ("enterprise", "mobile", "ics").
    include_description: Whether to include campaign descriptions.

Returns:
    {
      "group": {
          "attack_id": "GXXXX" | null,
          "name": "<group name or null>",
          "stix_id": "<intrusion-set--UUID>",
          "description": "<text or null>"
      } | null,

      "count": <number of campaigns>,

      "campaigns": [
        {
          "attack_id": "CXXXX" | null,
          "name": "<campaign name>",
          "stix_id": "<campaign--UUID>",
          "description": "<text or null>"
        },
        ...
      ],

      "formatted": "<formatted human-readable block>",
      "message": "<status summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
group_stix_idYes
include_descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description fully carries the burden. It explains the purpose, parameters, and details the return structure including fields like 'group', 'count', 'campaigns', 'formatted', and 'message'. It also provides context that campaigns are specific operations attributed to a threat group. No side effects or destructive behavior are indicated, which aligns with 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 an intro, Args section, and Returns section (a pseudo-output schema). It is front-loaded with the main purpose. While concise, it could be slightly shorter without losing clarity, but it earns its length by providing important parameter and return details.

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 complexity (3 parameters, no annotations), the description is extremely complete. It includes parameter details, return structure, and operational context. The presence of an output schema in the description further enhances completeness. An agent has all the information needed to correctly invoke the tool.

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?

The input schema has 0% description coverage, but the description compensates thoroughly by explaining each parameter: 'group_stix_id' is described as a STIX UUID with an example, 'domain' lists allowed values, and 'include_description' clarifies its boolean purpose. This adds essential meaning beyond the schema's bare types and titles.

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 specifies the verb 'Get', the resource 'campaigns', and the scope 'attributed to a specific intrusion set', with a note on STIX ID identification. It distinguishes itself from sibling tools like `get_all_campaigns` and `get_campaigns_by_alias` by focusing on attribution to a specific group.

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 provides context that the tool is for campaigns attributed to a specific group, implying usage when the agent has a group STIX ID. However, it lacks explicit alternative guidance or when-not-to-use scenarios, though the context is clear enough for an agent to decide.

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