Skip to main content
Glama
po4erk91

Thread Keeper

by po4erk91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mp_health

Read-only

Check the health of every running Thread Keeper server process and daemon thread. Identifies orphaned processes by parent status and heartbeat age, and reports liveness verdicts.

Instructions

Diagnostic snapshot of every running thread-keeper server process on this machine. Shows pid, parent status, RSS, heartbeat age, and whether each is classified as orphaned (parent gone + no fresh heartbeat from its session).

Self (the process answering this call) is always marked is_self=true and never flagged as orphan. The text view also includes each registered daemon thread's liveness verdict. Returns structuredContent (MpHealth) plus the legacy text block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
liveNo
totalNo
orphansNo
processesNo
rss_total_mbNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.14.0
    • addedOutput schema / $defs
      Added value: +{
+  "MpProcess": {
+    "additionalProperties": true,
+    "properties": {
+      "etime": {
+        "default": "",
+        "title": "Etime",
+        "type": "string"
+      },
+      "heartbeat_age_s": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Heartbeat Age S"
+      },
+      "is_orphaned": {
+        "default": false,
+        "title": "Is Orphaned",
+        "type": "boolean"
+      },
+      "is_self": {
+        "default": false,
+        "title": "Is Self",
+        "type": "boolean"
+      },
+      "orphan_reason": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Orphan Reason"
+      },
+      "parent_alive": {
+        "default": false,
+        "title": "Parent Alive",
+        "type": "boolean"
+      },
+      "pid": {
+        "title": "Pid",
+        "type": "integer"
+      },
+      "ppid": {
+        "default": 0,
+        "title": "Ppid",
+        "type": "integer"
+      },
+      "rss_kb": {
+        "default": 0,
+        "title": "Rss Kb",
+        "type": "integer"
+      }
+    },
+    "required": [
+      "pid"
+    ],
+    "title": "MpProcess",
+    "type": "object"
+  }
+}
    • addedOutput schema / description
      Added value: +"Snapshot of every running thread-keeper server process on the host."
    • addedOutput schema / properties / live
      Added value: +{
+  "default": 0,
+  "title": "Live",
+  "type": "integer"
+}
    • addedOutput schema / properties / orphans
      Added value: +{
+  "default": 0,
+  "title": "Orphans",
+  "type": "integer"
+}
    • addedOutput schema / properties / processes
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/MpProcess"
+  },
+  "title": "Processes",
+  "type": "array"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "title": "Result",
-  "type": "string"
-}
    • addedOutput schema / properties / rss_total_mb
      Added value: +{
+  "default": 0,
+  "title": "Rss Total Mb",
+  "type": "integer"
+}
    • addedOutput schema / properties / total
      Added value: +{
+  "default": 0,
+  "title": "Total",
+  "type": "integer"
+}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • changedOutput schema / title
      Previous value: -"mp_healthOutput"New value: +"MpHealth"
  2. First observedv0.13.2

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses specific behavioral traits: self-identification with is_self=true, the guarantee that self is never flagged as orphan, inclusion of daemon thread liveness in the text view, and the return format (structuredContent plus legacy text block). This is rich, non-obvious context that the annotation alone does not 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?

The description is four sentences with no filler. It front-loads the core purpose, then adds specific details that are all relevant to understanding behavior and output. Every sentence earns its place, and the length is proportional to the tool's simplicity.

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?

With no parameters, a readOnlyHint annotation, and an output schema present, the description covers all necessary invocation knowledge. It explains the key output fields, self-handling logic, and return transport, so an agent can invoke and interpret the call without ambiguity.

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 input schema is empty, so there are no parameters to document; the schema coverage is trivially 100%. Per the baseline for 0-parameter tools, the description need not add parameter-specific guidance. It appropriately avoids inventing parameter details that don't exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: 'Diagnostic snapshot of every running thread-keeper server process on this machine.' It enumerates the specific fields shown (pid, parent status, RSS, heartbeat age, orphan classification), making the tool's scope concrete. However, it does not explicitly distinguish itself from siblings like mp_dashboard or live_status, so it stops short of a 5.

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 phrase 'Diagnostic snapshot' implies the tool is for inspecting process health, and the zero-parameter signature makes it low-risk. But the description never explicitly states when to prefer this over alternatives such as mp_dashboard, whoami, or live_status, nor does it give exclusions. Usage is implied rather than directly guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools