Skip to main content
Glama
threadlinqs-cmd

Intel Threadlinqs MCP

by threadlinqs-cmd
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Health Check

health
Read-onlyIdempotent

Confirm API reachability and key validity, then retrieve platform counts and the latest debrief date to verify integration readiness.

Instructions

Lightweight liveness probe: confirms the API is reachable and your key is valid, and returns platform counts + the latest debrief date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes'ok' | 'degraded'
tool_countNoTools the LIVE server exposes. If your client listed fewer, its catalog is stale.
catalog_hintNo
prompt_countNo
wire_versionNoNegotiated MCP protocol version.
api_reachableNo
catalog_sourceNoAlways 'live' here — this response came from the server, not a cached catalog.
platform_statsNo
server_versionNo
latest_debrief_dateNo
min_recommended_clientNo

Schema Changelog

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

  1. Changed6 schema fields changedv8.2.1
    • addedOutput schema / properties / catalog_hint
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / catalog_source
      Added value: +{
+  "description": "Always 'live' here — this response came from the server, not a cached catalog.",
+  "type": "string"
+}
    • addedOutput schema / properties / min_recommended_client
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / prompt_count
      Added value: +{
+  "type": "integer"
+}
    • addedOutput schema / properties / tool_count
      Added value: +{
+  "description": "Tools the LIVE server exposes. If your client listed fewer, its catalog is stale.",
+  "type": "integer"
+}
    • addedOutput schema / properties / wire_version
      Added value: +{
+  "description": "Negotiated MCP protocol version.",
+  "type": "string"
+}
  2. Changed7 schema fields changedv8.1.1
    • addedOutput schema / properties / api_reachable
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / latest_debrief_date
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / platform_stats
      Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}
    • addedOutput schema / properties / server_version
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / status / description
      Added value: +"'ok' | 'degraded'"
    • removedOutput schema / properties / version
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / required
      Added value: +[
+  "status"
+]
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish that the tool is read-only, idempotent, and non-destructive. The description adds useful behavioral context by noting that key validity is checked and that platform counts plus the latest debrief date are returned. There is no contradiction with 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?

The description is a single, well-front-loaded sentence that conveys the tool's purpose, scope, and outputs without filler. Every clause earns its place.

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?

Given the tool has no parameters, rich annotations, and an output schema, the description is complete for a health-check tool. It tells the agent what the call verifies and what data comes back, and 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?

The tool takes zero parameters, so there are no parameter semantics for the description to clarify. The schema is already fully straightforward, giving a baseline of 4; the description does not need to compensate for any missing parameter documentation.

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 states a specific purpose: it is a lightweight liveness probe that confirms API reachability and key validity, and it names what it returns (platform counts and latest debrief date). This clearly distinguishes it from the many data-retrieval sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage as a lightweight connectivity and credential check, but it does not explicitly say when to prefer this over siblings like get_platform_stats or get_latest_debrief, nor does it state when not to use it. The guidance is inferred rather than explicit.

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