Skip to main content
Glama
threadlinqs-cmd

Intel Threadlinqs MCP

by threadlinqs-cmd
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Tool Intelligence

get_tool_intelligence
Read-onlyIdempotent

Look up any offensive tool, utility, RMM, or LOLBin by name to get its class, prevalence, associated threats and actors, and common MITRE ATT&CK techniques.

Instructions

Pivot on an offensive tool / utility / RMM / LOLBin by name (e.g. "Cobalt Strike", "Mimikatz", "AnyDesk", "PsExec"). Returns the canonical tool + class, prevalence, the threats and actors using it, and its most-common ATT&CK techniques. prevalence.actor_count is the TRUE distinct-actor total; the actors[] array is clipped to the top 20 (see prevalence.actors_returned) — do not read its length as the population.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTool name (e.g. "Cobalt Strike", "Mimikatz")

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: -"Tool name (e.g. Cobalt Strike, Mimikatz)"New value: +"Tool name (e.g. \"Cobalt Strike\", \"Mimikatz\")"
    • 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
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description surfaces a critical behavioral nuance: prevalence.actor_count is the true distinct-actor total, while the actors[] array is clipped to the top 20 and must not be mistaken for the full population. This is genuinely useful behavioral guidance.

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?

The description is compact and well-structured: an actionable purpose sentence, an output summary sentence, and a focused data-read confusion caveat. Every sentence earns its place and no structured schema details are merely repeated.

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?

For a one-parameter lookup with a full input schema and an output schema present, the description provides all needed context: what kinds of names are valid, what is returned, and how to interpret prevalence counts. No critical clarity gap remains.

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 input schema already defines the single 'name' parameter, and the description expands it by narrowing the valid domain to offensive tools/utilities/RMMs/LOLBins and providing concrete examples. This adds value beyond the schema's generic 'Tool name' description.

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 states a specific, actionable operation: pivot by tool name and return canonical tool data, class, prevalence, threats, actors, and ATT&CK techniques. It gives examples that distinguish it from sibling intelligence tools like get_malware_intelligence or get_actor_intelligence.

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?

It clearly defines when to use this tool: when you need intelligence about an offensive tool, utility, RMM, or LOLBin by name. It does not explicitly contrast with sibling tools, but its domain and input expectations are concrete enough to route an agent correctly.

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