Skip to main content
Glama
threadlinqs-cmd

Intel Threadlinqs MCP

by threadlinqs-cmd
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Get Changelog

get_changelog
Read-onlyIdempotent

Retrieve the platform changelog for new threats, detections, and features. Read newest-first entries by date with a configurable limit, and check staleness indicators to avoid relying on an outdated feed.

Instructions

Get the platform changelog (new threats, detections, features), strictly newest-first by date. Pass limit (default 20, max 100). NOTE: this is a hand-maintained release feed, not a deploy log — it stopped being written in Feb 2026, so the response carries latest_entry_date / stale_days / a warning. For what the platform actually looks like NOW use get_platform_stats (live corpus counts) and get_engine_status (pipeline state); do not answer "what changed recently" from this alone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax entries (default 20, max 100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
staleNo
totalNo
entriesYes
warningNoPresent when the feed is stale; says what it does NOT cover.
has_moreNo
stale_daysNo
latest_entry_dateNoDate of the newest entry — the feed cut-off.

Schema Changelog

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

  1. Changed10 schema fields changedv8.2.1
    • addedOutput schema / properties / count
      Added value: +{
+  "type": "integer"
+}
    • addedOutput schema / properties / entries
      Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "changes": {
+        "items": {},
+        "type": "array"
+      },
+      "date": {
+        "type": "string"
+      },
+      "id": {},
+      "title": {
+        "type": "string"
+      },
+      "version": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / has_more
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / latest_entry_date
      Added value: +{
+  "description": "Date of the newest entry — the feed cut-off.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "properties": {
-      "changes": {
-        "items": {},
-        "type": "array"
-      },
-      "id": {}
-    },
-    "type": "object"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / stale
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / stale_days
      Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • addedOutput schema / properties / total
      Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • addedOutput schema / properties / warning
      Added value: +{
+  "description": "Present when the feed is stale; says what it does NOT cover.",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "entries"
+]
  2. Changed2 schema fields changedv8.1.1
    • changedInput schema / properties / limit / description
      Previous value: -"Max entries (default 20)"New value: +"Max entries (default 20, max 100)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "result": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "changes": {
+            "items": {},
+            "type": "array"
+          },
+          "id": {}
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "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?

The description discloses that this is a hand-maintained release feed, not a deploy log, that it stopped being written in Feb 2026, and that the response carries latest_entry_date, stale_days, and a warning. This is valuable behavioral context well beyond what the idempotent/read-only annotations provide.

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?

Every sentence earns its place: the resource and ordering constraint, the parameter guidance, and the critical staleness warning with alternatives. The most decision-relevant caveat is front-loaded and clearly formatted with NOTE.

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 simple one-parameter read tool with an output schema, the description is fully sufficient: it explains the data source, staleness, expected response markers, and directs the agent to the correct sibling tools. Nothing needed for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents limit with default and max values, and schema description coverage is 100%. The description restates 'Pass limit (default 20, max 100)' but adds no new semantic meaning beyond reinforcing that the parameter is optional.

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 clearly states this tool returns the platform changelog — new threats, detections, and features — ordered strictly newest-first by date. It goes beyond a mere restatement of the name by specifying the content scope and ordering behavior.

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 tells the agent when to avoid relying on this tool: for current platform state, use get_platform_stats or get_engine_status instead. It also warns not to answer 'what changed recently' from this feed alone, giving clear routing guidance relative to sibling tools.

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