Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_campaigns_by_alias

Resolve campaign aliases to find official MITRE ATT&CK campaigns using alternate names from different vendors.

Instructions

Get campaigns by their alias.

Campaigns frequently have multiple names assigned by different vendors
or research teams. This function resolves those aliases.

Args:
    alias: Campaign alias or alternate name (case-insensitive)
    domain: ATT&CK domain ("enterprise", "ics", etc.)
    include_description: Include campaign descriptions in output

Returns:
    {
      "alias": "<requested name>",
      "count": int,
      "campaigns": [
        {
          "name": "...",
          "stix_id": "<campaign--UUID>",
          "attack_id": "Cxxxx" | null,
          "description": "..." | null
        },
        ...
      ],
      "formatted": "<multi-line readable text>",
      "message": "<summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aliasYes
domainNoenterprise
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 full burden. It details the return format, case-insensitivity of alias, and optional parameters. However, it does not mention error handling or behavior when alias is not found, though the output schema implies a message field.

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 a header, explanation, and Args/Returns sections. It is appropriately sized for a tool with 3 parameters and an output schema. Could be slightly more concise but no wasted sentences.

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 complexity (3 params, output schema, many siblings), the description covers purpose, alias resolution, parameter details, and return structure. Missing explicit error handling or edge cases, but overall complete for a get operation.

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%, so the description must explain parameters. It does so effectively: alias is described as case-insensitive, domain is 'ATT&CK domain', and include_description is 'Include campaign descriptions in output'. This adds full meaning beyond the schema 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 states the verb 'Get' and resource 'campaigns by their alias', distinguishing from sibling tools like 'get_campaigns_attributed_to_group' or 'get_campaigns_using_software'. The explanation of alias resolution adds specificity.

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 on when to use this tool ('resolve aliases') but does not explicitly exclude alternatives or state when not to use it. Sibling tools exist for different filters, so a comparative note would be helpful.

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