Skip to main content
Glama
threadlinqs-cmd

Intel Threadlinqs MCP

by threadlinqs-cmd
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Get Roadmap

get_roadmap
Read-onlyIdempotent

Get the platform roadmap with completed, in-progress, and planned items, counts, and timestamps. Check stale_days and confirm with live tool data to avoid reporting outdated statuses.

Instructions

Get the Threadlinqs Intelligence platform roadmap: completed, in_progress and ideas (planned), with counts, generated_at and as_of. WARNING: this table is hand-maintained and has not been updated since Feb 2026 — the response carries stale_days and a warning, and several items still marked "planned" have since shipped. Do not report an item as unbuilt on this basis; confirm with get_started (live tool catalog), get_platform_stats or get_engine_status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_ofNoLast date the roadmap table itself was edited.
ideasNo
staleNo
countsNo
warningNoPresent when stale; says the statuses are unreconciled.
completedNo
stale_daysNo
in_progressNo
generated_atNoWhen this response was produced.

Schema Changelog

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

  1. Changed7 schema fields changedv8.2.1
    • addedOutput schema / properties / as_of
      Added value: +{
+  "description": "Last date the roadmap table itself was edited.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / counts
      Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "completed": {
+      "type": "integer"
+    },
+    "ideas": {
+      "type": "integer"
+    },
+    "in_progress": {
+      "type": "integer"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / generated_at
      Added value: +{
+  "description": "When this response was produced.",
+  "type": "string"
+}
    • addedOutput schema / properties / in_progress
      Added value: +{
+  "items": {},
+  "type": "array"
+}
    • addedOutput schema / properties / stale
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / stale_days
      Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • addedOutput schema / properties / warning
      Added value: +{
+  "description": "Present when stale; says the statuses are unreconciled.",
+  "type": "string"
+}
  2. Changed1 schema field changedv8.1.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "completed": {
+      "items": {},
+      "type": "array"
+    },
+    "ideas": {
+      "items": {},
+      "type": "array"
+    }
+  },
+  "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?

Annotations already declare readOnlyHint and idempotentHint true, and the description adds meaningful behavioral context beyond them: the data is stale, a stale_days field and warning are returned, and several planned items have already shipped. This transparency is critical to accurate agent behavior.

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 compact and front-loaded, with the core resource and fields stated first and the important staleness warning placed immediately after. Every sentence adds essential information, with no filler or repetition of schema details.

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 parameterless read-only tool with an output schema and rich annotations, this description fully covers what an agent need aware of. It explains the data source, staleness, response warning, and which sibling tools to use for authoritative status checks.

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?

The tool has no parameters, so the schema provides no parameter semantics to clarify. The description adds value by listing the output fields such as completed, in_progress, ideas, counts, generated_at, as_of, and stale_days, which supports expectation-setting for the response.

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 identifies the exact resource and verb: retrieving the Threadlinqs Intelligence platform roadmap. It enumerates the statuses and fields returned, so an agent knows precisely what information the tool provides and can distinguish it from other catalog/status 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?

The description explicitly warns that the roadmap is hand-maintained and stale, and instructs the agent to confirm current build status with get_started, get_platform_stats, or get_engine_status instead. This gives clear when-not-to-use guidance and names specific 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