Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_techniques_used_by_group

Retrieve all ATT&CK techniques used by a specific APT group using its STIX ID. Returns technique details and relationships for threat intelligence analysis.

Instructions

Get all techniques used by a specific APT group, identified by its STIX ID.

This is similar to `get_group_techniques`, but instead of a group name or
alias it takes the group's STIX UUID (e.g. "intrusion-set--..."), which is
useful when you already have the STIX ID from another query or relationship.

Args:
    group_stix_id: STIX ID of the group (intrusion-set--UUID).
    domain: ATT&CK domain ("enterprise", "mobile", "ics").
    include_description: Whether to include technique descriptions.

Returns:
    {
      "group": {
          "attack_id": "GXXXX" | null,
          "name": "<group name or null>",
          "stix_id": "<intrusion-set--UUID>",
          "description": "<text or null>"
      } | null,
      "count": <number of techniques>,
      "techniques": [
        {
          "attack_id": "TXXXX or TXXXX.YYY" | null,
          "name": "<technique name>",
          "stix_id": "<attack-pattern--UUID>",
          "description": "<text or null>",
          "relationships": [
            {
              "stix_id": "<relationship--UUID>",
              "relationship_type": "uses",
              "description": "<relationship description or null>",
              "source_ref": "<source STIX ID>",
              "target_ref": "<target STIX ID>"
            },
            ...
          ]
        },
        ...
      ],
      "formatted": "<human-readable technique list>",
      "message": "<status summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
group_stix_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 provided, so description carries full burden. It details the return structure comprehensively, including null fields and example values. Lacks mention of potential errors, rate limits, or side effects, but for a read query the output transparency is strong.

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?

Well-structured with bullet points for return format. Front-loaded with purpose. Each sentence adds value without redundancy. Concise given the complexity of the tool.

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 complexity (3 parameters, detailed output), the description fully explains inputs, defaults, and return structure. Comprehensive without being verbose.

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 coverage is 0%, description fully compensates by explaining each parameter: `group_stix_id` format, `domain` default, `include_description` default, and the expected STIX ID pattern. Adds essential meaning beyond raw 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), resource (techniques used by group), and distinguishes from sibling tool `get_group_techniques` by specifying use of STIX ID instead of name. Purpose is specific and unambiguous.

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?

Explicitly compares to `get_group_techniques` and advises using this tool when STIX ID is known. While it doesn't list when not to use, it provides clear context for choosing this tool over alternatives.

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