Skip to main content
Glama
threadlinqs-cmd

Intel Threadlinqs MCP

Export ATT&CK Navigator Layer

export_attack_navigator
Read-onlyIdempotent

Generate a MITRE ATT&CK Navigator layer (enterprise-attack) as a heatmap of technique coverage, scored by count of threats using each technique, for one actor or platform-wide.

Instructions

Export a MITRE ATT&CK Navigator layer (enterprise-attack) for visualization. Pass actor= to score techniques attributed to one actor, or all=true for platform-wide coverage. score is PER TECHNIQUE — the number of corpus threats using it (for the actor, or platform-wide) — so the heatmap ranks within a tactic, not just between tactics; the unit is stated in the layer's description and metadata. Returns {name, versions, domain, description, techniques:[{techniqueID, score, color, comment}], gradient, metadata}. Capped at 600 techniques; when the tail is dropped, metadata carries a 'truncated' entry saying so. ATLAS (AML.*) and non-enterprise ids are excluded, since the layer domain is enterprise-attack.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNoIf true, build a platform-wide coverage layer from MITRE coverage instead of a single actor
actorNoThreat-actor name or alias whose techniques to score (e.g. "APT29")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
domainNo
gradientNo
metadataNo
versionsNo
techniquesYes
descriptionNoIncludes the scoring unit ("Score = …").
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds non-obvious behavioral detail beyond those: score is per technique accounting for corpus threats, ranking is within a tactic, the layer is capped at 600 techniques and may carry a 'truncated' entry, and ATLAS/non-enterprise IDs are excluded. These are important for correct interpretation.

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 dense and front-loaded with the primary purpose, but includes a full returned-structure list that duplicates the output schema. That sentence is slightly redundant, but otherwise every sentence earns its place and there is no filler.

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?

Given branch annotations and output schema exist, the description completely covers non-obvious behavioral details: the meaning of 'score', how the two modes differ, truncation behavior, exclusions, and the exact matching between parameters and use cases. Nothing critical is missing.

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%, so the schema already documents both parameters. The description largely mirrors that information and adds only a scoring context rather than substantially enriching individual parameter semantics.

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 uses a specific verb and resource: 'Export a MITRE ATT&CK Navigator layer (enterprise-attack) for visualization.' It clearly distinguishes this tool from siblings like export_stix or get_mitre_coverage by naming the exact artifact and domain scope.

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?

The description explicitly tells the agent to 'pass actor=<name>' for actor-level coverage or 'all=true' for platform-wide coverage, which is clear usage guidance for the two parameters. It does not explicitly enumerate when not to use this tool versus neighboring export/get_mitre tools, so it stops short of a full 5.

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/threadlinqs-cmd/intelthreadlinqs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server