Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_all_techniques

Retrieve all MITRE ATT&CK techniques for enterprise, mobile, or ICS domains. Optionally exclude revoked techniques or include descriptions for comprehensive threat intelligence.

Instructions

Get all ATT&CK techniques for a given domain.

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

Returns:
    {
      "domain": "<domain>",
      "count": <number of techniques>,
      "techniques": [
        {
          "attack_id": "TXXXX or TXXXX.YYY",
          "name": "<technique name>",
          "stix_id": "<attack-pattern--UUID>",
          "description": "<text or null>",
          "tactics": [ "<tactic 1>", "<tactic 2>", ... ]
        },
        ...
      ],
      "formatted": "<optional human-readable output>",
      "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 the return structure via an output schema and describes parameter effects. However, it does not mention any behavioral traits such as permissions, rate limits, or side effects (though the tool is read-only, this is not explicitly stated).

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 concise with a clear purpose followed by Args in a bullet-like format and a Returns block. Every sentence contributes value; no unnecessary text.

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 complexity (3 parameters, many siblings, output schema provided), the description covers the essential aspects: purpose, parameters, and return structure. It lacks explicit usage guidance against siblings, but the output schema compensates for return value clarity.

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?

With 0% schema description coverage, the description adds meaning by explaining each parameter (domain: ATT&CK domain with allowed values; remove_revoked_deprecated: exclude deprecated; include_description: include descriptions). This goes beyond the schema's names 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 explicitly states 'Get all ATT&CK techniques for a given domain', which is a specific verb+resource combination. It includes the domain parameter and optional filters, clearly distinguishing it from sibling tools that target specific subsets like techniques by tactic or platform.

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 techniques for a domain, but does not explicitly mention when to use this tool versus alternatives (e.g., get_techniques_by_tactic, get_techniques_by_platform). No exclusions or when-not guidance are 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