Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_stix_type

Identify the STIX object type (technique, malware, etc.) from any STIX ID in a specified ATT&CK domain.

Instructions

Determine the STIX object type for a given STIX ID.

This is useful when you have a raw STIX UUID (e.g.,
"attack-pattern--xxxx") but need to know whether it corresponds to a
technique, intrusion set, malware, tool, mitigation, data source, etc.

Args:
    stix_id: The STIX UUID identifier to look up.
    domain: ATT&CK domain ("enterprise", "mobile", "ics").

Returns:
    {
        "found": bool,
        "stix_type": "<type string or null>",
        "message": "<status message>"
    }

Examples:
    get_stix_type("attack-pattern--a62a8db3-f23a-4d8f-afd6-9dbc77e7813b")
    → "attack-pattern"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
stix_idYes

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 carries full burden. It discloses the return format (found, stix_type, message) and gives an example. It does not discuss error handling or side effects, but for a simple lookup tool, the provided information is sufficient.

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 concise and well-structured with sections for purpose, usage, parameters, return value, and an example. It is front-loaded with the main purpose. Every sentence adds value without unnecessary repetition.

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 simplicity, no output schema (but description provides return format), and sibling tools that might overlap, the description is complete. It covers the tool's function, parameters, return structure, and a concrete example, ensuring an agent can invoke it correctly.

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 schema has 0% description coverage (no descriptions for properties), but the tool's description includes an 'Args' section that explains both parameters: stix_id (required, STIX UUID) and domain (optional, default 'enterprise'). The example further clarifies usage, fully compensating for the schema gap.

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's purpose: 'Determine the STIX object type for a given STIX ID.' It distinguishes from siblings by specifying that it only returns the type, not the full object, and gives context about when it's useful (e.g., STIX UUID like 'attack-pattern--xxxx').

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 explicitly says when to use the tool: when you have a STIX ID and need to know its type. It does not mention alternatives or when not to use it, but the context is clear enough for an agent to infer usage.

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