Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_tactics_by_matrix

Retrieve all tactics from an ATT&CK matrix by providing its STIX ID and domain. Optionally include tactic descriptions for detailed analysis.

Instructions

Get all ATT&CK tactics belonging to a specific matrix.

Args:
    matrix_stix_id: STIX ID of the matrix (e.g., x-mitre-matrix--UUID)
    domain: ATT&CK domain ('enterprise', 'mobile', 'ics')
    include_description: Whether to include tactic descriptions

Returns:
    {
      "found": bool,
      "count": int,
      "tactics": [
        {
          "name": "...",
          "stix_id": "...",
          "description": "...",
          "attack_id": "TAxxxx" or null
        }
      ],
      "formatted": "<multiline string>",
      "message": "..."
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
matrix_stix_idYes
include_descriptionNo
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 describes the return format in detail, which is helpful. However, it does not disclose whether the tool is read-only, requires authentication, or has any side effects. For a straightforward read operation, this 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is highly concise: a one-line summary followed by structured Args and Returns sections. Every sentence adds value, and the most critical information (the action) is front-loaded. No fluff or repetition.

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?

The tool has 3 parameters and no output schema. The description fully covers the input parameters and provides a detailed return structure including types and field names. It explains the 'found' field and formatted output. Minor gap: no example of expected UUID format for matrix_stix_id, but overall complete for the tool's complexity.

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%, meaning the schema titles provide minimal meaning. The description compensates by explicitly explaining each parameter in the Args block (matrix_stix_id, domain, include_description), including default values and expected format hints. This adds significant meaning 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 clearly states the action ('Get all ATT&CK tactics'), the resource ('tactics'), and the constraint ('belonging to a specific matrix'). This distinguishes it from sibling tools like get_all_tactics (no filter) and get_tactics_by_technique (different filter).

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?

The description does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. There is no mention of prerequisites or fallback options. Given the many sibling tools, this lack of guidance is a significant gap.

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