Skip to main content
Glama
Montimage

mitre-mcp

by Montimage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get Tactics

get_tactics
Read-onlyIdempotent

Retrieve MITRE ATT&CK tactics for enterprise, mobile, or ICS domains, with options to exclude revoked or deprecated items and control result count for efficient querying.

Instructions

Get tactics from the MITRE ATT&CK framework with token-optimized responses.

Args: ctx: FastMCP request context (injected by the server) domain: Domain to query (enterprise-attack, mobile-attack, or ics-attack) remove_revoked_deprecated: Remove revoked or deprecated objects limit: Maximum number of tactics to return (default: 20) offset: Index to start from when returning tactics (for pagination)

Returns: Dictionary containing a list of tactics and pagination metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
domainNoenterprise-attack
offsetNo
remove_revoked_deprecatedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tacticsYes
paginationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.4.0
    • addedInput schema / properties / domain / enum
      Added value: +[
+  "enterprise-attack",
+  "mobile-attack",
+  "ics-attack"
+]
    • addedInput schema / properties / limit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Limit"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "title": "Offset",
+  "type": "integer"
+}
    • addedOutput schema / $defs
      Added value: +{
+  "Pagination": {
+    "description": "Pagination metadata returned alongside paged list results.",
+    "properties": {
+      "has_more": {
+        "title": "Has More",
+        "type": "boolean"
+      },
+      "limit": {
+        "title": "Limit",
+        "type": "integer"
+      },
+      "offset": {
+        "title": "Offset",
+        "type": "integer"
+      },
+      "total": {
+        "title": "Total",
+        "type": "integer"
+      }
+    },
+    "required": [
+      "total",
+      "offset",
+      "limit",
+      "has_more"
+    ],
+    "title": "Pagination",
+    "type": "object"
+  },
+  "TacticResult": {
+    "description": "Single tactic entry in get_tactics results.",
+    "properties": {
+      "description": {
+        "title": "Description",
+        "type": "string"
+      },
+      "id": {
+        "title": "Id",
+        "type": "string"
+      },
+      "name": {
+        "title": "Name",
+        "type": "string"
+      },
+      "shortname": {
+        "title": "Shortname",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "shortname",
+      "description"
+    ],
+    "title": "TacticResult",
+    "type": "object"
+  }
+}
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / description
      Added value: +"get_tactics result."
    • addedOutput schema / properties
      Added value: +{
+  "pagination": {
+    "$ref": "#/$defs/Pagination"
+  },
+  "tactics": {
+    "items": {
+      "$ref": "#/$defs/TacticResult"
+    },
+    "title": "Tactics",
+    "type": "array"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "tactics",
+  "pagination"
+]
    • changedOutput schema / title
      Previous value: -"get_tacticsDictOutput"New value: +"TacticsResult"
  2. First observedv0.3.1

TDQS

B3.4/5.0
Behavior3/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 some context by mentioning token-optimized responses and pagination metadata, but it does not elaborate on how token optimization works or what pagination metadata is returned. This is acceptable but leaves room for more transparency.

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 well-structured with a clear one-line summary, a compact Args block, and a Returns line. It avoids fluff and front-loads the purpose. The inclusion of ctx as an argument that is not in the schema is slightly extraneous but quickly clarified as injected by the server.

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

Completeness4/5

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

For a simple list-retrieval tool with an output schema and rich annotations, the description covers the essential information: purpose, parameters, and return shape. It does not mention how to choose this tool over siblings, but given the simplicity and output schema, it is largely complete. The limit default inconsistency is the main gap.

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?

The schema has 0% description coverage, but the description's Args section compensates by explaining domain, remove_revoked_deprecated, limit, and offset. It adds meaning beyond the schema (e.g., what 'remove revoked or deprecated' does, what 'offset' is for). However, there is a discrepancy: the description says the limit default is 20, while the schema states default null, which could confuse an agent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Get tactics') and a clear resource ('MITRE ATT&CK framework'), which is unambiguous. However, it does not explicitly distinguish itself from sibling tools like get_techniques or get_techniques_by_tactic, though the resource name is inherently informative.

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 explicit guidance on when to use this tool versus its siblings. There is no mention of alternatives, exclusions, or preferred use cases beyond stating that it retrieves tactics. The sibling tool names are visible in context but not referenced in the description itself.

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

Deploy Server

Other Tools