Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_all_software

Retrieve all software (malware and tools) from a specified MITRE ATT&CK domain, with options to exclude revoked or deprecated entries and include descriptions.

Instructions

Get all software (malware and tools) in a domain.

This is effectively an alias for the MITRE helper get_software(), but it
returns structured results suitable for LLMs and clients.

Args:
    domain: ATT&CK domain ("enterprise", "mobile", "ics").
    remove_revoked_deprecated: Whether to exclude revoked/deprecated software.
    include_description: Whether to include descriptions.

Returns:
    {
      "domain": "<domain>",
      "count": <number of software objects>,
      "software": [
        {
          "attack_id": "<SXXXX or similar> | null",
          "name": "<software name>",
          "aliases": [...],
          "stix_id": "<malware--UUID or tool--UUID>",
          "type": "<malware|tool|...>",
          "description": "<text or null>"
        },
        ...
      ],
      "formatted": "<optional human-readable listing>",
      "message": "<summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
include_descriptionNo
remove_revoked_deprecatedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/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 discloses that the tool is an alias for get_software() and returns structured results, and includes a detailed return format. However, it does not explicitly state that the operation is read-only, safe, or any side effects, though the context suggests it is non-destructive.

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 clear first line, followed by an Args and Returns section. It is slightly lengthy but every sentence adds value. Could be more concise, but it is effectively organized.

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?

Given the tool's simplicity (3 optional parameters, no required params), the description is comprehensive. It covers purpose, parameters, and return format in detail. The output schema is provided in the Returns section, making it complete for an LLM to use.

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 compensates fully by documenting all three parameters in an Args section: domain, remove_revoked_deprecated, and include_description, explaining their purpose and defaults.

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 'Get all software (malware and tools) in a domain.' It specifies the resource (software) and the scope (all in a domain). It distinguishes itself from the sibling 'get_software' by noting it is an alias that returns structured results suitable for LLMs and clients.

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 for retrieving all software in a domain with optional filters, but it does not explicitly state when to use this tool over alternatives like 'get_software', 'search_software', or other sibling tools. No when-not or alternative guidance is provided.

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