Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_datacomponents_detecting_technique

Get data components that can detect a specific MITRE ATT&CK technique by traversing relationships or resolving data sources.

Instructions

Get all data components that can detect a specific technique.

Primary mode:
  - Use mitreattack-python relationship traversal (if present)

Fallback mode (when relationship traversal yields 0):
  - Read technique.x_mitre_data_sources (strings)
  - Resolve data source objects by name
  - Return data components whose x_mitre_data_source_ref points to those data sources
  - If the string includes a component name (e.g., "Process: Process Creation"),
    filter to that component when possible.

Returns the same structure as before, plus a debug block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
technique_stix_idYes
include_descriptionNo
Behavior3/5

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

Beyond annotations (none provided), the description discloses the two operational modes, fallback logic, and the addition of a debug block. However, it does not mention side effects, authentication requirements, or rate limits. For a read-only tool, this is adequate but incomplete.

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 relatively concise and well-structured, using clear sections for primary and fallback modes. It avoids unnecessary verbiage, though the bullet list could be slightly more compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema or annotations, the description is insufficient. It does not describe the return format, debug block content, or clarify 'same structure as before'. Parameter descriptions are absent, leaving major gaps for invocation.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, and the tool description does not explain any of the three parameters ('domain', 'technique_stix_id', 'include_description'). The description discusses data source resolution but not parameter meaning or usage.

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 it retrieves data components that detect a specific technique. It specifies the resource ('data components') and verb ('Get'), and distinguishes from reverse tools like get_techniques_detected_by_datacomponent. The primary and fallback modes are outlined.

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 two modes (primary and fallback) with conditions for use. It details fallback logic when relationship traversal yields zero results. However, it does not explicitly mention when to use this tool versus its reverse counterpart, 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