Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_techniques_by_platform

Retrieve all MITRE ATT&CK techniques that apply to a specific platform and domain. Optionally include technique descriptions.

Instructions

Get all ATT&CK techniques that apply to a specific platform.

Args:
    platform: Platform name (e.g., 'Windows', 'Linux', 'macOS', 
              'Cloud', 'Azure AD', 'Network', etc.)
    domain: ATT&CK domain ('enterprise', 'mobile', 'ics').
    include_description: Whether to include technique descriptions.

Returns:
    {
      "platform": "<platform>",
      "count": <number>,
      "techniques": [
        {
          "attack_id": "Txxxx" or "Txxxx.xxx" or null,
          "name": "<technique name>",
          "stix_id": "<attack-pattern--UUID>",
          "description": "<text or null>"
        },
        ...
      ],
      "formatted": "<optional formatted string>",
      "message": "<summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
platformYes
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, the description must bear the full burden. It implies a read-only operation via 'Get' and documents return format, but does not disclose authentication needs, rate limits, or side effects. 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 well-structured with a header sentence, parameter list, and return schema. It is informative without unnecessary fluff, though the return schema is somewhat lengthy.

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's moderate complexity and presence of an output schema (documented in description), the description covers purpose, parameters, and return format. It lacks error handling or rate limit info, but is sufficient for basic usage.

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 adds detailed parameter documentation: platform examples, domain values, and include_description semantics. This significantly compensates for the schema gap, though it could provide more constraint information.

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 ATT&CK techniques that apply to a specific platform,' using a specific verb and resource. It differentiates from sibling tools like get_technique_by_id or get_techniques_by_tactic by focusing on platform filtering.

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 provides no guidance on when to use this tool versus alternatives like get_techniques_by_tactic or search_techniques. It does not specify prerequisites or excluded use cases.

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