Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_all_datasources

Retrieve all MITRE ATT&CK data sources for a specified domain, with options to exclude revoked or deprecated sources and include descriptions.

Instructions

Get all ATT&CK data sources in a domain.

Data sources represent *what* kind of telemetry you collect
(e.g., Process Monitoring, Network Traffic, File Monitoring).

Args:
    domain: ATT&CK domain ("enterprise", "mobile", "ics").
    remove_revoked_deprecated: Whether to exclude revoked/deprecated data sources.
    include_description: Whether to include descriptions.

Returns:
    {
      "domain": "<domain>",
      "count": <number of data sources>,
      "datasources": [
        {
          "name": "<data source name>",
          "stix_id": "<x-mitre-data-source--UUID>",
          "description": "<text or null>",
          "platforms": ["<Windows>", "<Linux>", ...]  # if available
        },
        ...
      ],
      "formatted": "<optional human-readable output>",
      "message": "<summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
include_descriptionNo
remove_revoked_deprecatedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses the read-only nature (get all), explains parameters and return format in detail. It does not mention rate limits or auth, but the behavior is transparent and no contradictions exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with clear sections (purpose, explanation, args, returns) but is slightly verbose. The extra explanation of what data sources are is helpful for context. Every sentence adds value, but could be more concise.

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 (3 optional params, list return), the description is fully complete. It covers the operation, parameters, and output format in detail. The output schema is described, so no gaps remain.

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%, but the description adds full meaning: domain values, remove_revoked_deprecated and include_description behavior, defaults. It explains each parameter's purpose completely, compensating for the lack of schema descriptions.

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 'Get all ATT&CK data sources in a domain.' It explains what data sources are, and the tool name distinguishes it from siblings like 'get_all_datacomponents'. The purpose is specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when needing all data sources for a domain, but provides no explicit guidance on when to use this tool vs alternatives like 'get_all_datacomponents' or other get-all tools. No when-not-to-use or prerequisites are mentioned.

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