Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_name

Resolve a STIX ID to its human-readable ATT&CK object name. Converts UUIDs like attack-pattern--UUID into names such as 'Phishing'.

Instructions

Resolve the human-readable object name for a given STIX ID.

This converts internal STIX UUIDs such as:
    attack-pattern--UUID
    intrusion-set--UUID
    malware--UUID
    tool--UUID
    course-of-action--UUID

into ATT&CK object names such as:
    "Phishing"
    "APT29"
    "Cobalt Strike"
    "Valid Accounts"

Args:
    stix_id: STIX UUID of the object.
    domain: ATT&CK domain ("enterprise", "mobile", "ics").

Returns:
    {
      "found": bool,
      "name": "<object name or null>",
      "message": "<status message>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
stix_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/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 details input/output structure and examples, but does not disclose side effects, required permissions, safety profile, or limitations. The tool appears to be a simple lookup, but behavioral traits like read-only nature are not explicitly stated.

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 separate sections for purpose, input examples, parameter listing, and return format. It is appropriately sized, front-loading the main action, and every sentence adds value. No redundant or vague statements.

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 and the presence of an output schema, the description is complete. It covers the conversion logic, parameter specifics, return format with fields, and status codes via the message field. No missing critical details.

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

Parameters4/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. It defines both parameters (stix_id, domain) with concrete examples and expected values. The domain parameter's default and possible values are implied, but not exhaustive. This adds meaning beyond the bare schema 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's purpose: 'Resolve the human-readable object name for a given STIX ID.' It provides concrete examples of input and output, making the conversion specific and immediately understandable. This distinguishes it from sibling tools that retrieve full objects or lists.

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 when to use the tool (when you have a STIX ID and need the readable name) and gives context on the types of STIX IDs and domains. It does not explicitly state when not to use it or mention alternatives, but the examples and parameter listing provide implicit guidance.

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