Skip to main content
Glama
threadlinqs-cmd

Intel Threadlinqs MCP

List Actors

search_actors
Read-onlyIdempotent

Find threat actors by filtering on tool, malware, or sector and review aggregate stats, severity, categories, and nation-state details. Use for attribution and triage.

Instructions

List attributed threat actors with aggregate stats (threat_count, severity levels, categories, nation_state). Returns the full roster in one call, or narrow it with the optional tool / malware / sector filters (e.g. tool="Cobalt Strike" → only actors that used it). Use get_actor for a single actor's full profile. Not paginated; the response carries a total count. Names are REPAIRED before they are returned: the corpus stores threat_actor as free text and comma-split it, so prose fragments and truncated parentheticals used to appear as adversaries — label_hygiene reports what was dropped and repaired. Two per-row flags matter: role: "co-mention" means the corpus never files a threat under that name as its primary attribution, and also_grounded_as means the corpus also records the name as a malware family or tool (e.g. SNOWLIGHT). Check both before reporting a row as an operator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolNoOnly actors with a threat using this tool (e.g. "Cobalt Strike")
sectorNoOnly actors with a threat targeting this sector (e.g. "Healthcare")
malwareNoOnly actors with a threat deploying this malware family (e.g. "LockBit")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalNoTotal matching rows, when the handler reports one.
actorsNo
has_moreNoTrue when another page may exist.
next_cursorNoOpaque cursor for the next page, or null when this is the last page or the endpoint ignores offset.
label_hygieneNo

Schema Changelog

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

  1. Changed4 schema fields changedv8.2.1
    • addedOutput schema / properties / actors / items / properties / also_grounded_as
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / actors / items / properties / merged_from
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / actors / items / properties / role
      Added value: +{
      +  "description": "primary = the corpus files at least one threat under this name. co-mention = it only ever appears alongside another actor, so it may be a mis-split label rather than an operator.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / label_hygiene
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "actors": {
      +      "type": "integer"
      +    },
      +    "dropped": {
      +      "description": "Labels rejected as comma-split sentence fragments, not adversaries.",
      +      "type": "integer"
      +    },
      +    "dropped_labels": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "raw_labels": {
      +      "type": "integer"
      +    },
      +    "repaired": {
      +      "description": "Labels whose truncated parenthetical was trimmed back to the name.",
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed8 schema fields changedv8.1.1
    • removedInput schema / properties / limit
      Removed value: -{
      -  "description": "Max results (default 20)",
      -  "type": "number"
      -}
    • changedInput schema / properties / malware / description
      Previous value: -"Only actors with a threat deploying this malware family (e.g. 'LockBit')"New value: +"Only actors with a threat deploying this malware family (e.g. \"LockBit\")"
    • removedInput schema / properties / motivation
      Removed value: -{
      -  "description": "Filter by motivation (e.g. 'financial', 'espionage', 'destruction')",
      -  "type": "string"
      -}
    • removedInput schema / properties / nation_state
      Removed value: -{
      -  "description": "Filter by nation-state (e.g. 'Russia', 'China', 'Iran')",
      -  "type": "string"
      -}
    • removedInput schema / properties / query
      Removed value: -{
      -  "description": "Search term (actor name or alias)",
      -  "type": "string"
      -}
    • changedInput schema / properties / sector / description
      Previous value: -"Only actors with a threat targeting this sector (e.g. 'Healthcare')"New value: +"Only actors with a threat targeting this sector (e.g. \"Healthcare\")"
    • changedInput schema / properties / tool / description
      Previous value: -"Only actors with a threat using this tool (e.g. 'Cobalt Strike')"New value: +"Only actors with a threat using this tool (e.g. \"Cobalt Strike\")"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "actors": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "motivation": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "description": "Canonical actor name — pass to get_actor.",
      +            "type": "string"
      +          },
      +          "nation_state": {
      +            "type": "string"
      +          },
      +          "threat_count": {
      +            "type": "integer"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "has_more": {
      +      "description": "True when another page may exist.",
      +      "type": "boolean"
      +    },
      +    "next_cursor": {
      +      "description": "Opaque cursor for the next page, or null when this is the last page or the endpoint ignores offset.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "total": {
      +      "description": "Total matching rows, when the handler reports one.",
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses data-repair behavior, label_hygiene reporting, the meaning of role: co-mention and also_grounded_as, and non-pagination with a total count. This meaningfully helps an agent interpret returned rows correctly.

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 more verbose than average, but every sentence earns its place: purpose, filtering, sibling routing, pagination, and two critical data-quality warnings. It is front-loaded with the main verb and resource.

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 listing tool, it covers the full behavioral envelope: default and filtered behavior, single-actor alternative, output size expectations, and interpretation of per-row flags. The existing output schema carries the mechanical return shape, so nothing critical is missing.

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?

Schema coverage is 100% and each parameter has a one-line description, so the baseline is 3. The description adds semantic clarity by showing that filters narrow the full roster and provides a concrete example of how filtering behaves.

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 opens with a specific verb and resource: 'List attributed threat actors with aggregate stats,' and explicitly contrasts itself with get_actor for single-actor profiles. It immediately distinguishes itself from sibling actor tools.

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?

It explicitly explains both modes: full roster in one call versus narrowing via optional filters, provides a concrete example with tool='Cobalt Strike', and directs users to get_actor for single-actor detail. It also states the pagination behavior, leaving no guesswork.

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