Skip to main content
Glama
threadlinqs-cmd

Intel Threadlinqs MCP

by threadlinqs-cmd
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Get Threat Bundle

get_threat_bundle
Read-onlyIdempotent

Fetch a bundled dossier for a threat: details, simulations, and transcripts in one request to reduce API round-trips. Include 'summary' to get just the threat.

Instructions

One-shot dossier for a threat: threat detail plus its simulations and pipeline transcripts (include="summary" returns just the threat). Fewer round-trips than get_threat + get_threat_simulations + get_threat_transcripts separately. The threat is the same bounded projection get_threat returns by default — call get_threat(id, sections="all") for the unabridged record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeNo"full" (default) bundles simulations + transcripts; "summary" returns just the threat
threat_idYesThreat ID (e.g. TL-2026-0042)
simulation_limitNoPlaybooks to embed, 1-20 (default 3). Each carries full command text; raise only if you need more than the newest few.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
threatYes
simulationsNo
transcriptsNoOmitted entirely when include='summary'.

Schema Changelog

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

  1. Changed1 schema field changedv8.2.1
    • addedInput schema / properties / simulation_limit
      Added value: +{
+  "description": "Playbooks to embed, 1-20 (default 3). Each carries full command text; raise only if you need more than the newest few.",
+  "type": "integer"
+}
  2. Changed4 schema fields changedv8.1.1
    • changedInput schema / properties / include / description
      Previous value: -"Response detail level: 'full' (default) or 'summary' (id, title, severity, MITRE only)"New value: +"\"full\" (default) bundles simulations + transcripts; \"summary\" returns just the threat"
    • removedInput schema / properties / include / enum
      Removed value: -[
-  "full",
-  "summary"
-]
    • changedInput schema / properties / threat_id / description
      Previous value: -"Threat ID (e.g., TL-2026-0356)"New value: +"Threat ID (e.g. TL-2026-0042)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "simulations": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "threat": {
+      "additionalProperties": true,
+      "properties": {
+        "id": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "transcripts": {
+      "description": "Omitted entirely when include='summary'.",
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "threat"
+  ],
+  "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?

The annotations already declare readOnly, idempotent, non-destructive behavior. The description adds value beyond these annotations by explaining the bounded nature of the returned threat projection, the effect of include='summary', and that it bundles multiple data sources into one response. This is transparent about behavior without contradicting the annotations.

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?

Three sentences, each earning its place: the first defines the bundle, the second explains its round-trip advantage, and the third clarifies the bounded nature and points to an alternative. It is front-loaded with the core purpose and avoids redundancy or 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?

For a read-only bundled tool with a full output schema and complete parameter schemas, this description covers all necessary agent guidance: what the bundle includes, how to narrow the response, when to use alternatives, and how the bundled 'threat' compares to get_threat's default projection. Nothing essential 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%, so the baseline is 3. The description adds useful content beyond the schema: include='summary' yields just the threat, simulation_limit embeds full command text, and the warning to raise the limit only when needing more than the newest few playbooks. These clarifications make the parameter semantics easier to apply correctly.

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: 'One-shot dossier for a threat: threat detail plus its simulations and pipeline transcripts.' It clearly distinguishes itself from the component calls it bundles (get_threat + get_threat_simulations + get_threat_transcripts), and clarifies that include='summary' returns just the threat.

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 states when this tool is preferable ('Fewer round-trips than get_threat + get_threat_simulations + get_threat_transcripts separately') and names the alternative for an uncompressed record ('call get_threat(id, sections="all") for the unabridged record'). This gives an agent a concrete decision rule.

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