Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_technique_by_id

Retrieve any MITRE ATT&CK technique by its external ID from enterprise, mobile, or ICS domains, returning structured data and a human-readable description for threat intelligence workflows.

Instructions

" Retrieve a MITRE ATT&CK technique by its external ATT&CK ID (e.g., "T1055", "T1053.005").

This tool searches the specified ATT&CK domain (enterprise, mobile, or ics)
and returns both structured machine-readable data and an optional formatted
human-readable text block. It is useful for user-facing responses as well
as downstream programmatic reasoning.

Args:
    technique_id: The external ATT&CK technique ID (e.g., "T1055").
    domain: ATT&CK domain to search in ("enterprise", "mobile", "ics").
    include_description: If True, returns the full ATT&CK description text.

Returns:
    {
      "found": bool,
      "technique": {
          "id": "<ATT&CK ID>",
          "name": "<technique name>",
          "stix_id": "<STIX object ID>",
          "description": "<full description or null>"
      },
      "formatted": "<human-readable formatted block>",
      "message": "<status message>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
technique_idYes
include_descriptionNo

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 must disclose behaviors. It specifies the tool searches enterprise, mobile, and ICS domains and returns optional description and formatted text. It does not mention side effects or auth, but the read-only nature is implied.

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 concisely structured with a summary, then a detailed paragraph, followed by Args and Returns sections. Every sentence provides value without redundancy.

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 3 parameters, no enums, and an output schema present, the description is complete. It covers purpose, parameters, and return format, and is self-contained for agent 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%, so the description must compensate fully. It explains all three parameters (technique_id, domain, include_description) with examples and default values, and details the return structure.

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 it retrieves a MITRE ATT&CK technique by external ID, provides an example, and distinguishes from sibling tools like get_all_techniques or get_techniques_by_tactic by specifying it fetches a single technique.

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 explains it is useful for user-facing responses and programmatic reasoning, but does not explicitly state when not to use it or suggest alternatives. It implicitly guides usage by describing the function.

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