Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_procedure_examples_by_technique

Provides procedure examples showing how threat groups have used a specific ATT&CK technique, with optional incident descriptions.

Instructions

Get procedure examples showing how threat groups used a specific technique.

Procedure examples describe real incident behavior tied to this technique.

Args:
    technique_stix_id: STIX UUID of the technique
    domain: ATT&CK domain
    include_description: Include descriptions of the examples if available

Returns:
    {
      "technique": {
          "attack_id": "Txxxx",
          "name": "...",
          "stix_id": "attack-pattern--UUID"
      },
      "count": N,
      "examples": [
          {
            "relationship_id": "relationship--UUID",
            "source_group_attack_id": "Gxxxx",
            "source_group_name": "...",
            "description": "...",
            "stix_id": "relationship--UUID"
          },
          ...
      ],
      "formatted": "<multi-line readable text>",
      "message": "<summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
technique_stix_idYes
include_descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided. The description does not disclose any behavioral traits such as side effects, authentication requirements, rate limits, or idempotency. It only states that the tool returns procedure examples, which is minimal behavioral context.

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 concise with only a few lines. It includes a docstring summarizing parameters and return value. However, it could be more structured (e.g., separating usage from return format). No fluff.

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 has 3 parameters and an output schema (provided in the description), the description is fairly complete. It explains the purpose, parameters, and return format. It could mention valid domain values, but overall adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 add meaning. It lists the parameters in a docstring but does not explain what values are valid for domain (e.g., 'enterprise', 'mobile') or what include_description truly does. The description adds little beyond the parameter names and types.

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 tool retrieves procedure examples for a specific technique, with a verb 'Get' and resource 'procedure examples by technique'. It distinguishes from sibling tools like get_procedure_examples_by_tactic by specifying 'by technique' in the name and description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is used for looking up procedure examples for a given technique, but does not explicitly state when to use it versus alternatives (e.g., get_procedure_examples_by_tactic) or provide any exclusions. No guidance is given on prerequisites or context.

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