Intel Threadlinqs MCP

Campaign Intelligence

get_campaign_intelligence

Read-onlyIdempotent

Get campaign intelligence by name, covering threats, actors, prevalence, and ATT&CK techniques. Use the membership breakdown to distinguish grounded entries from title-based leads before confirming membership.

Instructions

Pivot on a named campaign / operation by name (e.g. "Snowflake campaign", "ClickFix"). Returns the threats in the campaign, the actors involved, prevalence, and common ATT&CK techniques. Membership is the UNION of the curated threat_campaign_refs table and threats whose own TITLE names the campaign, because the curated table is thin (ClickFix: 7 curated rows against 57 threats that name it). Each threat carries matched_via (grounded | title | grounded+title) and the response carries a membership breakdown — neither source is complete, so treat title rows as leads and check them before calling them members.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Campaign / operation name

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No
`actors`	No
`matched`	Yes
`threats`	No
`canonical`	No
`membership`	No
`prevalence`	No
`entity_type`	No
`top_techniques`	No

Schema Changelog

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

Changed5 schema fields changedv8.2.1Aug 24, 2026

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"
+}

Changed1 schema field changedv8.1.1Aug 3, 2026

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"
+}

First observedv0.1.0Jul 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes beyond annotations by explaining how membership is computed (the lightweight UNION of curated references and threats matching by title), warns that the curated table is thin, names the `matched_via` field values, and tells the agent to treat title-matched rows as leads. This is excellent behavioral disclosure.

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 dense but every sentence serves a purpose: core action, output contents, membership source, and important caveat about trustworthiness. The warning about title rows is essential and the ClickFix example justifies why the union is needed.

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?

A given output schema handles return shape, and the description fully covers what the tool does, how membership is sourced, and how to treat results. Nothing important needed by an agent deciding to call or trust it 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?

With 100% schema coverage, the schema already documents the name parameter. The description adds extra value through concrete examples like 'Snowflake campaign' and 'ClickFix' and clarifies that title-based matching also matters, helping the agent pick a good input.

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: 'Pivot on a named campaign / operation by name'. It lists concrete returns — threats, actors, prevalence, ATT&CK techniques — so an agent knows exactly what intelligence it will get for a named campaign.

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?

Usage context is clear: call this when you have a campaign name like 'Snowflake campaign' or 'ClickFix'. There is no explicit mention of when not to use it or comparison to sibling tools like list_campaigns or search_threats, so it does not reach 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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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