Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

search_techniques

Search MITRE ATT&CK techniques by keyword in their name or description. Returns matching techniques with IDs and optional descriptions for enterprise, mobile, or ICS domains.

Instructions

Search MITRE ATT&CK techniques by keyword in their name or description.

This tool performs a case-insensitive search over all non-revoked,
non-deprecated techniques in the given domain. A technique is matched if
the query string appears in either:
  • the technique name, or
  • the technique description

Examples:
    - search_techniques("PowerShell")
    - search_techniques("credential dumping")
    - search_techniques("initial access", domain="enterprise")

Args:
    query: Text to search for in technique names and descriptions.
    domain: ATT&CK domain ("enterprise", "mobile", or "ics").
    include_description: Whether to include descriptions in the structured
                         result and formatted output.

Returns:
    {
      "count": <number of matches>,
      "techniques": [
        {
          "attack_id": "<TXXXX or TXXXX.YYY>",
          "name": "<technique name>",
          "stix_id": "<attack-pattern--...>",
          "description": "<description or null>",
        },
        ...
      ],
      "formatted": "<human-readable formatted list>",
      "message": "<status summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
domainNoenterprise
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 bears full responsibility. It clearly states the tool's behavior: case-insensitive search, only non-revoked/non-deprecated techniques, matches in name or description, and returns a structured result with count, techniques list, formatted output, and message. It does not mention any destructive behavior or limitations, but it is transparent about the search criteria and output.

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 well-structured with clear sections, bullet points, examples, and a return value specification. It is concise and contains no unnecessary information, each sentence adds value.

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 has 3 parameters, no annotations, and an output schema, the description is complete. It covers purpose, usage guidelines, behavioral details, parameter semantics, and return format. It is a model description for an AI agent.

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. It fully describes all three parameters: query (text to search), domain (enterprise, mobile, or ics with default), and include_description (boolean, default true). It also provides examples and explains the return value structure, adding significant meaning beyond the 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 it searches MITRE ATT&CK techniques by keyword in name or description. It distinguishes from sibling tools like get_all_techniques (which returns all techniques) and other search tools (search_groups, search_software) by being specific to techniques and providing a keyword search.

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 that the tool performs a case-insensitive search over non-revoked, non-deprecated techniques. It provides examples and specifies the domain parameter. While it does not explicitly state when not to use it, the context of sibling tools implies alternatives, and the description gives clear guidance on its use.

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