Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_objects_modified_after

Query MITRE ATT&CK objects modified since a specified time to monitor framework updates.

Instructions

Get all ATT&CK objects modified after a specific timestamp.

Useful for tracking updates and changes to the ATT&CK framework.
Timestamp must be ISO8601 format, e.g., '2024-01-01T00:00:00Z'.

Returns:
    {
        "found": bool,
        "count": int,
        "objects": [
            {
                "id": "<ATT&CK ID or None>",
                "name": "...",
                "stix_id": "...",
                "type": "<stix-type>",
                "description": "..." | None
            },
            ...
        ],
        "formatted": "<pretty text>",
        "message": "..."
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
timestampYes
include_descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Provides timestamp format requirement and full output schema, but no annotations exist; lacks disclosure on side effects or authentication, which are minimal for a read operation.

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?

Concise with front-loaded purpose, usage hint, format note, and structured output schema. Every sentence adds value.

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?

Output schema covers return values, but missing parameter explanations for domain and include_description; additional context on scope or performance would help.

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

Parameters2/5

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

Only describes timestamp format; domain and include_description parameters are unexplained despite 0% schema coverage, leaving gaps for the agent.

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 clearly states the tool gets all ATT&CK objects modified after a timestamp, using a specific verb and resource, and distinguishes from siblings like get_objects_created_after.

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?

Describes use for tracking updates and changes, but does not explicitly specify when to use this tool versus alternatives or provide when-not conditions.

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