Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_all_matrices

Retrieve all ATT&CK matrices for a specified domain, with options to exclude revoked or deprecated matrices and include descriptions.

Instructions

Get all ATT&CK matrices in a domain.

Matrices are the top-level organizational structures in ATT&CK.
Each domain typically has one or more matrices
(e.g., Enterprise ATT&CK matrix).

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

Returns:
    {
      "domain": "<domain>",
      "count": <number of matrices>,
      "matrices": [
        {
          "attack_id": "<matrix ID or None>",
          "name": "<matrix name>",
          "stix_id": "<x-mitre-matrix--UUID>",
          "description": "<text or null>"
        },
        ...
      ],
      "formatted": "<optional human-readable output>",
      "message": "<summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
include_descriptionNo
remove_revoked_deprecatedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/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 format and the effect of each parameter, implying a read-only operation. The description does not explicitly state that the tool is safe and non-destructive, but the context and name suggest no side effects.

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 and well-structured: a one-line purpose, a brief contextual sentence, and a clear listing of arguments and return type. Every sentence is valuable and easy to parse.

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 parameters, output schema present), the description is thorough. It covers the domain options, parameter defaults, and the full return structure. The absence of annotations does not leave gaps.

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?

The input schema has 0% description coverage, but the tool description explains each parameter (domain, remove_revoked_deprecated, include_description) with clear meaning and default values, fully compensating for the lack of schema descriptions.

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 matrices in a domain') and specifies the resource (matrices). It explains what matrices are, distinguishing them from other sibling tools that retrieve different ATT&CK objects like techniques, groups, or software.

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 the tool (to retrieve matrices for a domain) and mentions that each domain typically has one or more matrices, implying a common use case. However, it does not explicitly state when not to use the tool or suggest alternative tools for similar purposes.

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