Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_objects_by_name

Retrieve MITRE ATT&CK objects by exact name match. Specify a STIX type and domain to get precise results for techniques, groups, or malware.

Instructions

Retrieve MITRE ATT&CK objects by exact name match (case-sensitive).

This tool performs an exact name match for a specific STIX type within
a given ATT&CK domain. It is more strict than generic search methods,
which typically perform partial or keyword matching.

Examples:
    - Technique: get_objects_by_name("Phishing", "attack-pattern")
    - Group: get_objects_by_name("APT29", "intrusion-set")
    - Malware: get_objects_by_name("Cobalt Strike", "malware")

Args:
    name: Exact object name to search for (case-sensitive).
    stix_type: STIX object type (same values as get_object_by_attack_id),
               e.g. "attack-pattern", "intrusion-set", "malware",
               "tool", "course-of-action", etc.
    domain: ATT&CK domain ("enterprise", "mobile", or "ics").
    include_description: Whether to include descriptions in the formatted output
                         and structured result.

Returns:
    {
      "count": <number of matching objects>,
      "objects": [
        {
          "attack_id": "<ATT&CK external ID or null>",
          "name": "<object name>",
          "stix_id": "<STIX ID>",
          "type": "<stix_type>",
          "description": "<description or null>"
        },
        ...
      ],
      "formatted": "<human-readable multi-object formatted text>",
      "message": "<status summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
domainNoenterprise
stix_typeYes
include_descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries the full burden. It thoroughly explains the tool's behavior: exact match, case-sensitive, returns structured results with count, objects, formatted text, and a message. No hidden side effects are omitted.

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 a clear overview, examples, parameter details, and return format. Every sentence contributes value, and the most important information is front-loaded.

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?

Even though an output schema exists, the description still fully documents the return structure. It covers all necessary aspects for the tool's purpose, leaving no gaps.

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?

The input schema has 0% description coverage, so the description fully compensates. It explains each parameter: name (exact name, case-sensitive), stix_type (with examples of valid types), domain (with options), and include_description (boolean, default false). This adds critical 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 the tool retrieves MITRE ATT&CK objects by exact name match, case-sensitive, and distinguishes itself from generic search methods by emphasizing strictness. Examples of usage with specific object types further clarify the purpose.

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 indicates the tool is for exact name matching and is more strict than generic search methods, implying when to use it. However, it does not explicitly state alternatives or when not to use this tool, leaving some ambiguity.

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