Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_object_by_stix_id

Retrieve a full MITRE ATT&CK object using its STIX ID to resolve relationships and get complete details.

Instructions

Retrieve any MITRE ATT&CK object by its STIX ID (UUID).

STIX IDs are internal identifiers like:
  - attack-pattern--a62a8db3-f23a-4d8f-afd6-9dbc77e7813b

This tool is useful when you already have a STIX ID from another
query or relationship and want to resolve it to the full object.

Args:
    stix_id: STIX object ID (e.g., "attack-pattern--...").
    domain: ATT&CK domain to search in ("enterprise", "mobile", "ics").
    include_description: Whether to include the object's description.

Returns:
    {
      "found": bool,
      "object": {
          "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 formatted text>",
      "message": "<status message>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
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 the description carries full burden. It discloses the return format with fields (found, object, formatted, message) and implies a read-only operation. More details on error handling or permissions could be added, but the core behavior is clear.

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 an intro, explanation, Args, and Returns. It is concise, front-loads the purpose, and every sentence adds value. No redundancy.

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 output schema exists (context: true), the description still covers return fields. Parameters are fully documented. The description is complete for resolving objects by STIX ID, covering purpose, usage, parameters, and output. 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?

Schema coverage is 0%, so the description must compensate. The 'Args' section explains each parameter: stix_id format, domain options ('enterprise', 'mobile', 'ics'), and include_description purpose. This adds 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 'Retrieve any MITRE ATT&CK object by its STIX ID (UUID).' This is a specific verb (retrieve) and resource (MITRE ATT&CK object) and distinguishes from siblings like 'get_object_by_attack_id' which uses a different identifier.

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 says 'This tool is useful when you already have a STIX ID from another query or relationship and want to resolve it to the full object.' This provides clear context for when to use it. It does not explicitly exclude cases or name alternatives, but the guidance is sufficient.

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