Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_campaigns_using_software

Find all campaigns associated with a specific malware or tool by providing its STIX ID and ATT&CK domain. Returns campaign details and relationships.

Instructions

Get all campaigns that use specific software/malware.

This is a reverse lookup: Software → Campaigns.

Args:
    software_stix_id: Software STIX UUID identifier (e.g., 'malware--UUID', 'tool--UUID').
    domain: ATT&CK domain ('enterprise', 'mobile', 'ics').
    include_description: Whether to include campaign descriptions.

Returns:
    {
      "software": {
          "attack_id": "SXXXX or similar" | null,
          "name": "<software name or null>",
          "stix_id": "<software STIX ID>",
          "type": "<malware|tool|...> or null",
          "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>",
          "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 campaigns>",
      "message": "<status summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
software_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 carries the full burden. It details the return structure comprehensively and indicates it is a read operation. However, it does not mention potential performance implications, pagination, or any side effects.

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?

The description is well-structured and concise, starting with a clear statement of purpose, followed by a brief conceptual note, then detailed but essential parameter and return descriptions. Every sentence adds value.

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?

Given the tool's moderate complexity and that an output schema is provided, the description is thorough. It covers inputs and outputs completely, but lacks explicit notes on how it differs from sibling tools or error handling scenarios.

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 compensates fully by providing clear descriptions for all three parameters, including format examples for software_stix_id and enumerating domain options.

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 tool's purpose: 'Get all campaigns that use specific software/malware.' It emphasizes 'reverse lookup: Software → Campaigns', which distinguishes it from sibling tools like get_campaigns_attributed_to_group or get_campaigns_using_technique.

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 by mentioning it's a reverse lookup, but it does not explicitly state when to use this tool versus alternatives. It lacks guidance on prerequisites or context where other tools might be more appropriate.

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