mitre-mcp

mitre_get_mitigation

Retrieve details on a mitigation and all techniques it addresses. This helps map defenses to adversarial techniques.

Instructions

Get details on a mitigation and all techniques it addresses

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mitigationId": "<mitigationId>"
    },
    "name": "mitre_get_mitigation"
  }
}

Input Schema

Name	Required	Description	Default
`mitigationId`	Yes	Mitigation ID (e.g., "M1036")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Jun 30, 2026

TDQS

B3.3/5.0

Behavior2/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 only states the tool gets details and techniques, but does not disclose what 'details' includes, any authentication needs, rate limits, or side effects. Minimal behavioral info.

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 a single sentence that conveys the core purpose without any unnecessary words. It is front-loaded and concise.

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

Completeness3/5

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

For a simple lookup tool with one parameter and no output schema, the description is minimally adequate. It mentions the output includes techniques, but lacks details on the full return structure. Could be improved but is not severely incomplete.

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

Parameters3/5

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

Schema coverage is 100% with the parameter 'mitigationId' documented. The description does not add additional meaning beyond the schema. Baseline 3 is appropriate since it adds no extra value for parameters.

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 verb (Get), the resource (mitigation), and the scope (details and all techniques it addresses). It distinguishes from siblings like mitre_mitigations_for_technique which does the reverse, and mitre_search_mitigations which searches.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like mitre_mitigations_for_technique or mitre_search_mitigations. No when-to-use or when-not-to-use information is given.

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