Skip to main content
Glama
threadlinqs-cmd

Intel Threadlinqs MCP

Get Threat

get_threat
Read-onlyIdempotent

Get a single threat's full dossier by ID—overview, attribution, MITRE techniques, IOCs, detection roster, timeline, targets, and tags—with optional section filtering to control response size.

Instructions

Get the detail for a single threat by its ID (e.g. TL-2026-0042): overview, attribution, MITRE techniques, IOCs, the detection roster, timeline, targets and tags. RETRIEVABLE IN PARTS — pass sections to choose what comes back; the response echoes _sections telling you what was returned and what was omitted. By default detection RULE BODIES (SPL/KQL/Sigma) are omitted — they are ~40% of a heavy dossier and have dedicated tools (export_detection / get_detection_detail) — and description is trimmed to 1500 chars with description_chars disclosing the true length. Pass sections="all" and max_description=-1 for the complete record. For malware families, tools, sectors/regions, OS and campaigns, call get_threat_enrichment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThreat ID (e.g. TL-2026-0042)
sectionsNoCSV of sections to return. Any of: overview, attribution, mitre, iocs, detections (WITH rule bodies), detections_meta (roster only, the default), timeline, tags, targets, remediation, references (full bibliography), references_compact (ranked primary-first + corroboration summary, in the default), similar, updates, osint, flow, entities — or "all", or "row" (exclusive: a ~500-byte identity row plus section counts). Default: overview,attribution,mitre,iocs,detections_meta,timeline,tags,targets,similar,flow,osint,references_compact
max_descriptionNoChar budget for the narrative description. Default 1500; 0 drops it; -1 returns it whole.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThreat ID (TL-YYYY-NNNN).
iocsNo
tagsNo
osintNoCommunity-OSINT summary; null below Red tier or when unscanned.
titleNo
statusNo
summaryNo
categoryNo
severityNo
_sectionsNo
created_atNo
detectionsNo
referencesNoFull bibliography. Present only under sections=references or sections=all.
updated_atNo
attributionNo
descriptionNo
identifiersNo
mitre_attackNo
description_charsNoTrue length of description when it was trimmed to max_description.
references_compactNoRanked primary-first, capped at 8. Present in the DEFAULT projection and in both bundles.
references_summaryNo
description_truncatedNo

Schema Changelog

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

  1. Changed8 schema fields changedv8.2.1
    • addedInput schema / properties / max_description
      Added value: +{
      +  "description": "Char budget for the narrative description. Default 1500; 0 drops it; -1 returns it whole.",
      +  "type": "number"
      +}
    • addedInput schema / properties / sections
      Added value: +{
      +  "description": "CSV of sections to return. Any of: overview, attribution, mitre, iocs, detections (WITH rule bodies), detections_meta (roster only, the default), timeline, tags, targets, remediation, references (full bibliography), references_compact (ranked primary-first + corroboration summary, in the default), similar, updates, osint, flow, entities — or \"all\", or \"row\" (exclusive: a ~500-byte identity row plus section counts). Default: overview,attribution,mitre,iocs,detections_meta,timeline,tags,targets,similar,flow,osint,references_compact",
      +  "type": "string"
      +}
    • addedOutput schema / properties / _sections
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "available": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "ignored_unknown": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "omitted": {
      +      "items": {
      +        "description": "Sections deliberately left out — re-call with sections=<name> to fetch them.",
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "returned": {
      +      "items": {
      +        "description": "Sections present in THIS response.",
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / description_chars
      Added value: +{
      +  "description": "True length of description when it was trimmed to max_description.",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / description_truncated
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / references / description
      Added value: +"Full bibliography. Present only under sections=references or sections=all."
    • addedOutput schema / properties / references_compact
      Added value: +{
      +  "description": "Ranked primary-first, capped at 8. Present in the DEFAULT projection and in both bundles.",
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "tier": {
      +        "description": "primary | research | secondary",
      +        "type": "string"
      +      },
      +      "type": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / references_summary
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "earliest_source_date": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "independent_domains": {
      +      "description": "Distinct registrable domains across ALL references — the corroboration count. Deliberately under-counted.",
      +      "type": "integer"
      +    },
      +    "latest_source_date": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "omitted": {
      +      "type": "integer"
      +    },
      +    "primary_count": {
      +      "type": "integer"
      +    },
      +    "total": {
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed20 schema fields changedv8.1.1
    • addedInput schema / properties / id
      Added value: +{
      +  "description": "Threat ID (e.g. TL-2026-0042)",
      +  "type": "string"
      +}
    • removedInput schema / properties / threat_id
      Removed value: -{
      -  "description": "Threat ID (e.g., TL-2026-0042)",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "threat_id"
      -]New value: +[
      +  "id"
      +]
    • addedOutput schema / properties / attribution
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "confidence": {
      +      "type": "string"
      +    },
      +    "motivation": {
      +      "type": "string"
      +    },
      +    "nation_state": {
      +      "type": "string"
      +    },
      +    "threat_actor": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / category
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / created_at
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / description
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / detections
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "detection_type": {
      +        "type": "string"
      +      },
      +      "id": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / id / description
      Added value: +"Threat ID (TL-YYYY-NNNN)."
    • addedOutput schema / properties / identifiers
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "aliases": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "cve": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "cwe": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / iocs
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / mitre_attack
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "tactic": {
      +        "type": "string"
      +      },
      +      "technique": {
      +        "type": "string"
      +      },
      +      "technique_id": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / osint
      Added value: +{
      +  "description": "Community-OSINT summary; null below Red tier or when unscanned.",
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / references
      Added value: +{
      +  "items": {},
      +  "type": "array"
      +}
    • addedOutput schema / properties / severity
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "cvss": {
      +      "type": "number"
      +    },
      +    "level": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / status
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / summary
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / tags
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / updated_at
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / required
      Added value: +[
      +  "id"
      +]
  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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds materially beyond that: the response echoes `_sections` to tell the caller what was returned/omitted, detection RULE BODIES are omitted by default (~40% payload), `description` is trimmed to 1500 chars with `description_chars` disclosing the true length, and the escape hatch of sections="all" + max_description=-1 for the full record. That is rich, non-redundant behavioral context.

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?

A dense but well-structured description: first sentence establishes the core purpose, then the behavioral flags (retrievable in parts, chunked payload, omitted rule bodies), then the escape hatch, then the routing to the enrichment sibling. Every sentence earns its place and the most decision-relevant facts are front-loaded. Not a word of 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 tool with an output schema, return values need no explanation, and the description covers the remaining behavioral gotchas: default sections, payload size implications, how to read the response via _sections, and how to get the full dossier. An agent has everything needed to invoke this tool correctly and to know precisely how to adjust behavior for different use cases. Nothing material 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 schema already documents id, sections, and max_description including literal defaults. The description adds real value on top by explaining WHY the trim exists (payload size), that max_description=-1 returns the whole record, and the detections vs detections_meta distinction in context. It's genuine added meaning, but the schema carries most of the parameter documentation burden, so 4 rather than 5.

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 names a specific verb ('Get the detail') targeting a single threat by ID, and enumerates the content: overview, attribution, MITRE techniques, IOCs, detection roster, timeline, targets, tags. It explicitly differentiates itself from siblings by pointing to get_threat_enrichment for malware/tool/sector/OS/campaign data and mentioning export_detection/get_detection_detail as the tools that handle rule bodies, so an agent can distinguish it from search_threats, get_recent_threats, and related 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 gives explicit routing guidance: detection rule bodies are omitted by default because they are ~40% of a heavy dossier and have dedicated tools (export_detection / get_detection_detail). It also states exactly when to use get_threat_enrichment ('For malware families, tools, sectors/regions, OS and campaigns, call...'). This is explicit when-to/not-to guidance with named alternatives.

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