mitre-mcp

mitre_campaign_profile

Build a technique profile from observed techniques to identify and attribute cyber campaigns.

Instructions

Build a technique profile from observed techniques for campaign analysis and attribution

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": {
      "techniques": "<techniques>"
    },
    "name": "mitre_campaign_profile"
  }
}

Input Schema

Name	Required	Description	Default
`techniques`	Yes	List of observed technique IDs (e.g., ['T1059.001', 'T1053.005'])

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 the full burden. It does not disclose whether the tool is read-only, destructive, or requires specific permissions. The verb 'Build' could imply creation, but typical MITRE tools are query-based, leading to ambiguity. No side effects or rate limits are mentioned.

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 a single, efficient sentence that immediately conveys the tool's purpose. It avoids unnecessary detail, but the brevity sacrifices usage guidance and behavioral context, which are needed for a complete understanding.

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, the description should describe what a 'technique profile' includes (e.g., counts, related campaigns, attribution scores). It does not, leaving the agent uncertain about the output. Sibling tools are numerous, and the description does not help differentiate. The tool is simple, but the description is incomplete for effective selection and invocation.

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 description coverage is 100%, with the 'techniques' parameter including an example format. The description adds minimal value beyond the schema by repeating 'from observed techniques'. Baseline 3 is appropriate as the schema already documents the parameter adequately.

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 'Build' and the resource 'technique profile from observed techniques' with a specific purpose 'for campaign analysis and attribution'. It distinguishes itself from sibling tools like mitre_get_campaign and mitre_search_campaigns by focusing on building a profile from a list of techniques rather than retrieving individual campaign details.

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 for campaign analysis but provides no explicit guidance on when to use this tool versus alternatives such as mitre_cross_correlate or mitre_technique_overlap. No exclusions or when-not-to-use scenarios are mentioned, leaving the agent to infer context.

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