Skip to main content
Glama
threadlinqs-cmd

Intel Threadlinqs MCP

by threadlinqs-cmd
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Malware Intelligence

get_malware_intelligence
Read-onlyIdempotent

Pivot on a malware family name to retrieve its type, prevalence, associated threats, actors, and common ATT&CK techniques.

Instructions

Pivot on a malware FAMILY by name (e.g. "LockBit", "Vidar", "Emotet"). Returns the canonical family + type, prevalence (threat/actor counts, first/last seen), the threats deploying it, the actors using it, and its most-common ATT&CK techniques. For an offensive TOOL (Cobalt Strike, Mimikatz) use get_tool_intelligence instead. Call resolve_entity first if unsure of the canonical name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesMalware family name (e.g. "LockBit", "Vidar")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
actorsNo
matchedYes
threatsNo
canonicalNo
membershipNo
prevalenceNo
entity_typeNo
top_techniquesNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv8.2.1
    • addedOutput schema / properties / membership
      Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "grounded": {
+      "type": "integer"
+    },
+    "note": {
+      "type": "string"
+    },
+    "title_match": {
+      "type": "integer"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / prevalence / properties / actor_count / description
      Added value: +"TRUE distinct-actor prevalence, uncapped. The actors[] array is clipped to 20 — compare with actors_returned."
    • addedOutput schema / properties / prevalence / properties / actors_returned
      Added value: +{
+  "type": "integer"
+}
    • addedOutput schema / properties / prevalence / properties / threat_count_is_floor
      Added value: +{
+  "description": "True when the membership fetch saturated, so threat_count under-counts.",
+  "type": "boolean"
+}
    • addedOutput schema / properties / threats / items / properties / matched_via
      Added value: +{
+  "description": "campaigns only: grounded | title | grounded+title",
+  "type": "string"
+}
  2. Changed2 schema fields changedv8.1.1
    • changedInput schema / properties / name / description
      Previous value: -"Malware family name (e.g. LockBit, Vidar)"New value: +"Malware family name (e.g. \"LockBit\", \"Vidar\")"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "actors": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "count": {
+            "type": "integer"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "canonical": {
+      "type": "string"
+    },
+    "entity_type": {
+      "type": "string"
+    },
+    "matched": {
+      "type": "boolean"
+    },
+    "prevalence": {
+      "additionalProperties": true,
+      "properties": {
+        "actor_count": {
+          "type": "integer"
+        },
+        "threat_count": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "query": {
+      "type": "string"
+    },
+    "threats": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "top_techniques": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "count": {
+            "type": "integer"
+          },
+          "technique_id": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "matched"
+  ],
+  "type": "object"
+}
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already establish readOnlyHint=true and idempotentHint=true, so the description does not need to repeat safety behavior. It adds genuinely useful behavioral context: the tool works from family names, resolves them to canonical entities, and returns prevalence plus related threats/actors/techniques. It does not describe error behavior for unknown names, but the output schema and read-only annotations lower the burden here.

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?

Every sentence earns its place: the first states purpose and input, the second lists return contents, and the third provides routing to the natural sibling. It is concise, front-loaded, and has 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?

With one required parameter, an output schema, and annotations covering side effects, the description includes everything operationally important: what type of input is accepted, what results are produced, the appropriate alternative, and the recommended disambiguation step. No critical invocation detail is missing for an agent to call this tool correctly.

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 already documents the only parameter 'name' at 100% coverage, so the baseline is 3. The description adds further meaning by clarifying that the value is a family, not a tool or actor, and by telling the agent to resolve non-canonical names beforehand. This gives the parameter real semantic depth beyond the schema example strings.

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 begins with a specific verb and resource: 'Pivot on a malware FAMILY by name'. It lists concrete return contents (canonical family, type, prevalence, threats, actors, ATT&CK techniques) and distinguishes itself from get_tool_intelligence, so an agent can immediately separate it from siblings.

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

Usage Guidelines5/5

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

The description explicitly tells when this tool is correct ('Pivot on a malware FAMILY') and when to choose the alternative: 'For an offensive TOOL (Cobalt Strike, Mimikatz) use get_tool_intelligence instead'. It also handles the ambiguous-name case by instructing 'Call resolve_entity first if unsure of the canonical name.'

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