Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_software_by_alias

Search for malware and tools by alias to identify software entries in MITRE ATT&CK, with details on attack ID, name, and aliases.

Instructions

Find software/malware by alias (e.g., 'Beacon', 'Mimilib').

Many malware/tools have multiple alternative names. This tool searches
the software catalog for alias matches.

Args:
    alias: Alias to search for.
    domain: ATT&CK domain ("enterprise", "mobile", "ics").
    include_description: Whether to include description fields.

Returns:
    {
      "alias": "<alias>",
      "count": <number of matches>,
      "software": [
        {
          "attack_id": "<SXXXX or MXXXX or None>",
          "name": "<software name>",
          "aliases": [...],
          "stix_id": "<malware--UUID or tool--UUID>",
          "type": "<malware|tool|...>",
          "description": "<text or null>"
        },
        ...
      ],
      "formatted": "<human readable output>",
      "message": "<status summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aliasYes
domainNoenterprise
include_descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/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 describes the search operation and return structure, but does not disclose side effects, permissions, or failure modes. It is adequate but not exhaustive.

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 concise with a clear summary followed by structured Args and Returns sections. It is front-loaded and efficient, though the documentation of returns partially overlaps with the output schema.

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 has 3 parameters and an output schema, the description is fairly complete: it explains purpose, parameters, return structure, and the context of aliases. It does not cover edge cases but is sufficient for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 an 'Args:' section that explains each parameter (alias, domain, include_description) beyond just the parameter names. This adds meaningful context.

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 'Find software/malware by alias' and explains that it searches the software catalog for alias matches. This is specific verb+resource and distinguishes from siblings like 'get_all_software' or 'search_software'.

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 when searching by an alias, noting that many tools have multiple names. However, it does not explicitly state when to use this tool versus alternatives like 'get_groups_by_alias' or 'get_campaigns_by_alias', nor does it provide exclusions.

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