Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_tactics_by_technique

Get all tactics (kill chain phases) linked to an ATT&CK technique by providing its STIX ID and domain. Returns tactic names, IDs, and optional descriptions.

Instructions

Get all tactics associated with a specific ATT&CK technique.

Techniques can belong to one or more tactics (kill chain phases).

Args:
    technique_stix_id: Technique STIX UUID identifier (attack-pattern--UUID)
    domain: ATT&CK domain ('enterprise', 'mobile', 'ics')
    include_description: Whether to include tactic descriptions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
technique_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 states the tool returns all tactics and includes the output structure with a 'found' flag for missing techniques. It does not mention any side effects, but as a read-only operation this is acceptable. However, it could be more explicit about the behavior when no technique is found.

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 very concise. It uses two short paragraphs and a clear Args/Returns structure. Every sentence adds information without redundancy. It is front-loaded with the core purpose.

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 no output schema, the description provides a detailed return structure. It covers the three parameters and the overall purpose. It lacks guidance on when to use this over similar sibling tools, but for its own functionality it is complete.

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?

The schema has 0% description coverage, so the description is the sole source. Each parameter is described with its type and purpose: technique_stix_id includes the expected UUID format, domain lists valid values, and include_description explains its boolean meaning. Defaults are not repeated but are implied by the schema. This adds value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves tactics for a specific technique. The verb 'get' and resource 'tactics' are specific. However, it does not explicitly distinguish from the very similar sibling 'get_technique_tactics', which could cause confusion.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_technique_tactics' or 'get_techniques_by_tactic'. There are no exclusions or context-specific recommendations.

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