Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_software_used_by_campaign

Retrieve all software and malware used in a campaign via its STIX ID, including names, types, and relationships, with optional descriptions.

Instructions

Get all software/malware 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 software descriptions.

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

      "count": <number of software objects>,

      "software": [
        {
          "attack_id": "SXXXX or similar" | null,
          "name": "<software name>",
          "stix_id": "<malware--UUID or tool--UUID>",
          "type": "<malware|tool|...> or null",
          "aliases": ["...", "..."],
          "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 software>",
      "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?

With no annotations, the description carries the full burden. It explains the parameters and provides a detailed return structure, including the formatted human-readable list and status message. However, it does not mention potential side effects or permissions requirements.

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 Args and Returns sections, but the inline output schema example is lengthy. The core purpose is front-loaded, but some detail could be streamlined without losing clarity.

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?

Despite the lack of annotations, the description provides complete guidance: all parameters are explained, and the return structure is fully specified. This enables correct invocation and interpretation of results.

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%, so the description must add meaning. It explains each parameter: campaign_stix_id (with example format), domain (with allowed values), and include_description (with default). This fully documents parameter semantics 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 begins with 'Get all software/malware used in a specific campaign,' clearly stating the verb and resource. This distinguishes it from siblings like get_software_used_by_group and get_campaigns_using_software, which target different entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description lacks explicit context on prerequisites (e.g., needing a campaign STIX ID) or situations where other tools like get_campaigns_using_software would 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