Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_techniques_used_by_campaign

Retrieve all techniques associated with a specific campaign by providing its STIX UUID and ATT&CK domain, with optional technique descriptions.

Instructions

Get all techniques used in a specific campaign.

Args:
    campaign_stix_id: Campaign STIX UUID identifier
                      (e.g., 'campaign--UUID').
    domain: ATT&CK domain ('enterprise', 'mobile', 'ics').
    include_description: Whether to include technique descriptions.

Returns:
    {
      "campaign": {
          "attack_id": "CXXXX" | null,
          "name": "<campaign name or null>",
          "stix_id": "<campaign--UUID>",
          "description": "<text or null>",
      } | null,

      "count": <number of techniques>,

      "techniques": [
        {
          "attack_id": "TXXXX or TXXXX.YYY" | null,
          "name": "<technique name>",
          "stix_id": "<attack-pattern--UUID>",
          "description": "<text or null>",
          "tactics": ["<Tactic 1>", "<Tactic 2>", ...],
          "relationships": [
            {
              "stix_id": "<relationship--UUID>",
              "relationship_type": "<type>",
              "description": "<relationship description or null>",
              "source_ref": "<source STIX ID>",
              "target_ref": "<target STIX ID>",
            },
            ...
          ]
        },
        ...
      ],

      "formatted": "<human-readable list of techniques>",
      "message": "<status summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
campaign_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?

No annotations are provided, so the description carries the full burden. It details the return structure comprehensively, including nested fields like relationships. However, it omits discussion of permissions, rate limits, or error conditions.

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-organized with Args and Returns sections. It is moderately long due to the detailed return schema, but each sentence provides necessary information. Some redundancy with the output schema is acceptable given its absence in the prompt.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the tool's purpose, parameters, and return structure comprehensively. It lacks mention of edge cases or potential errors, but given the tool's simplicity and the presence of an output schema, it is sufficient for accurate selection and invocation.

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 clear parameter explanations in the Args section, including type, purpose, and defaults (e.g., 'campaign_stix_id: Campaign STIX UUID identifier'). This fully compensates for the lack of 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 states 'Get all techniques used in a specific campaign', which is a clear verb+resource pairing. It distinguishes from sibling tools like get_techniques_used_by_group by explicitly targeting campaigns.

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 provide guidance on when to use this tool vs alternatives such as get_techniques_used_by_group or the inverse get_campaigns_using_technique. Users must infer from the name.

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