mitre-mcp

Get Technique by ID

get_technique_by_id

Read-onlyIdempotent

Retrieve a MITRE ATT&CK technique by its ID, such as T1055, from a chosen domain like enterprise, mobile, or ICS.

Instructions

Get a technique by its MITRE ATT&CK ID.

Args: ctx: FastMCP request context (injected by the server) technique_id: The MITRE ATT&CK ID of the technique (e.g., 'T1055') domain: Domain to query (enterprise-attack, mobile-attack, or ics-attack)

Returns: Dictionary containing the technique

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	No		enterprise-attack
`technique_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`technique`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.4.0Sep 21, 2026

addedInput schema / properties / domain / enum

Added value: +[
+  "enterprise-attack",
+  "mobile-attack",
+  "ics-attack"
+]

addedOutput schema / $defs

Added value: +{
+  "FormattedTechnique": {
+    "description": "Token-optimized technique object emitted by format_technique.",
+    "properties": {
+      "description": {
+        "title": "Description",
+        "type": "string"
+      },
+      "id": {
+        "title": "Id",
+        "type": "string"
+      },
+      "mitre_id": {
+        "title": "Mitre Id",
+        "type": "string"
+      },
+      "name": {
+        "title": "Name",
+        "type": "string"
+      },
+      "type": {
+        "title": "Type",
+        "type": "string"
+      }
+    },
+    "title": "FormattedTechnique",
+    "type": "object"
+  }
+}

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / description

Added value: +"get_technique_by_id result."

addedOutput schema / properties

Added value: +{
+  "technique": {
+    "$ref": "#/$defs/FormattedTechnique"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "technique"
+]
```

changedOutput schema / title

Previous value: -"get_technique_by_idDictOutput"New value: +"TechniqueResult"

First observedv0.3.1May 30, 2026

TDQS

A3.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond a generic 'Returns: Dictionary', offering no guidance on not-found behavior, error handling, or domain-specific effects.

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

Conciseness3/5

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

The first sentence is clear and front-loaded, but the docstring includes boilerplate about the injected ctx and a redundant 'Returns: Dictionary containing the technique' line that overlaps with the output schema. It is not bloated, yet not every sentence earns its place.

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?

For a simple read-only fetch by ID, the description covers both parameters, the domain choice, and the return shape. With an output schema present and readOnly/idempotent annotations, nothing needed to invoke the tool correctly is missing.

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 description coverage is 0%, so the description must compensate, and it does: it explains technique_id with a concrete example ('T1055') and lists the three valid domain values. This adds real meaning beyond the bare schema properties, though it does not elaborate on format edge cases.

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?

Description states an exact verb ('Get'), the resource ('technique'), and the key selector ('MITRE ATT&CK ID'), e.g., 'T1055'. This clearly distinguishes it from sibling tools like get_techniques or get_techniques_by_tactic without needing to open the schema.

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 the appropriate use case—call this when you already have a specific MITRE ATT&CK ID—but it never explicitly names alternatives or states when not to use it. No exclusions or comparison to sibling tools are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server