Thread Keeper

Overview Schema Related Servers Score Discussions

spawn_status

Read-only

Identify the CLI Thread Keeper detected as host and see how each spawn role resolves after env/file overrides, so you can confirm loops fire through the intended agent.

Instructions

Show which CLI thread-keeper detected as its host, and which CLI each spawn role resolves to (after env + file overrides). Use to sanity-check spawn config when you want loops to fire through a specific agent.

Resolution priority (highest first), all in ~/.threadkeeper/.env: • THREADKEEPER_SPAWN__LOOP__= • THREADKEEPER_SPAWN__DEFAULT= • active CLI detected at startup • final fallback: claude

Manual model pinning: • THREADKEEPER_SPAWN__MODEL__=

Manual reasoning effort: • THREADKEEPER_SPAWN__EFFORT__=

Returns structuredContent (SpawnStatus) plus the legacy text block.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`roles`	No
`active_cli`	No
`capabilities`	No
`role_resolution`	No
`catalog_generated_at`	No

Schema Changelog

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

Changed17 schema fields changedv0.17.0Aug 28, 2026

addedOutput schema / $defs / CliCapability / properties / catalog_age_s

Added value: +{
+  "default": 0,
+  "title": "Catalog Age S",
+  "type": "integer"
+}

addedOutput schema / $defs / CliCapability / properties / catalog_refreshed_at

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Catalog Refreshed At"
+}

addedOutput schema / $defs / CliCapability / properties / configured_effort

Added value: +{
+  "default": "",
+  "title": "Configured Effort",
+  "type": "string"
+}

addedOutput schema / $defs / CliCapability / properties / configured_model

Added value: +{
+  "default": "",
+  "title": "Configured Model",
+  "type": "string"
+}

addedOutput schema / $defs / CliCapability / properties / effort_mode

Added value: +{
+  "default": "independent",
+  "title": "Effort Mode",
+  "type": "string"
+}

addedOutput schema / $defs / CliCapability / properties / effort_note

Added value: +{
+  "default": "",
+  "title": "Effort Note",
+  "type": "string"
+}

addedOutput schema / $defs / CliCapability / properties / effort_options

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "title": "Effort Options",
+  "type": "array"
+}

addedOutput schema / $defs / CliCapability / properties / error

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Error"
+}

addedOutput schema / $defs / CliCapability / properties / executable

Added value: +{
+  "default": "",
+  "title": "Executable",
+  "type": "string"
+}

addedOutput schema / $defs / CliCapability / properties / model_source

Added value: +{
+  "default": "",
+  "title": "Model Source",
+  "type": "string"
+}

addedOutput schema / $defs / CliCapability / properties / models

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "title": "Models",
+  "type": "array"
+}

addedOutput schema / $defs / CliCapability / properties / source_updated_at

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Source Updated At"
+}

addedOutput schema / $defs / CliCapability / properties / stale

Added value: +{
+  "default": false,
+  "title": "Stale",
+  "type": "boolean"
+}

addedOutput schema / $defs / CliCapability / properties / version

Added value: +{
+  "default": "",
+  "title": "Version",
+  "type": "string"
+}

addedOutput schema / $defs / SpawnRoleResolution

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "cli": {
+      "title": "Cli",
+      "type": "string"
+    },
+    "cli_source": {
+      "default": "",
+      "title": "Cli Source",
+      "type": "string"
+    },
+    "effort": {
+      "default": "",
+      "title": "Effort",
+      "type": "string"
+    },
+    "effort_source": {
+      "default": "",
+      "title": "Effort Source",
+      "type": "string"
+    },
+    "model": {
+      "default": "",
+      "title": "Model",
+      "type": "string"
+    },
+    "model_source": {
+      "default": "",
+      "title": "Model Source",
+      "type": "string"
+    },
+    "role": {
+      "title": "Role",
+      "type": "string"
+    }
+  },
+  "required": [
+    "role",
+    "cli"
+  ],
+  "title": "SpawnRoleResolution",
+  "type": "object"
+}

addedOutput schema / properties / catalog_generated_at

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Catalog Generated At"
+}

addedOutput schema / properties / roles

Added value: +{
+  "items": {
+    "$ref": "#/$defs/SpawnRoleResolution"
+  },
+  "title": "Roles",
+  "type": "array"
+}

Changed8 schema fields changedv0.14.0Jun 25, 2026

addedOutput schema / $defs

Added value: +{
+  "CliCapability": {
+    "additionalProperties": true,
+    "properties": {
+      "available": {
+        "default": false,
+        "title": "Available",
+        "type": "boolean"
+      },
+      "bin": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Bin"
+      },
+      "cli": {
+        "title": "Cli",
+        "type": "string"
+      },
+      "note": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Note"
+      }
+    },
+    "required": [
+      "cli"
+    ],
+    "title": "CliCapability",
+    "type": "object"
+  }
+}

addedOutput schema / description

Added value: +"Detected host CLI plus per-role spawn resolution and capabilities."

addedOutput schema / properties / active_cli

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Active Cli"
+}

addedOutput schema / properties / capabilities

Added value: +{
+  "items": {
+    "$ref": "#/$defs/CliCapability"
+  },
+  "title": "Capabilities",
+  "type": "array"
+}

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

addedOutput schema / properties / role_resolution

Added value: +{
+  "default": "",
+  "title": "Role Resolution",
+  "type": "string"
+}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```

changedOutput schema / title

Previous value: -"spawn_statusOutput"New value: +"SpawnStatus"

First observedv0.13.2Jun 17, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The readOnlyHint annotation already signals safety, and the description adds substantial behavior beyond it: the exact resolution priority order, the fallback chain, environment variable override patterns, and that it returns both structuredContent and a legacy text block. This is valuable operational context an agent needs to interpret results correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, then organized into short bullet-like sections for resolution priority, model pinning, and effort. It is longer than minimal but every section carries useful diagnostic context; no fluff. Slightly dense but well structured.

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 zero-parameter diagnostic tool with an output schema and readOnlyHint, the description is complete. It explains resolution behavior, relevant environment variables, and the return shape, so an agent can invoke it and interpret results without further lookups.

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 zero parameters, so the schema leaves nothing to document. Baseline 4 applies; the description appropriately focuses on behavior rather than inventing parameter information.

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 uses a specific verb ('Show') with a clear resource (which CLI thread-keeper detected as host, and which CLI each spawn role resolves to). It explicitly frames itself as a sanity-check tool for spawn config, distinguishing it from spawn execution and other 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 Guidelines4/5

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

It states exactly when to use the tool: 'when you want loops to fire through a specific agent' to sanity-check spawn config. It does not explicitly name alternatives or exclusions, but the context and purpose are clear, and the zero-parameter diagnostic nature makes misuse unlikely.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/po4erk91/thread-keeper'

If you have feedback or need assistance with the MCP directory API, please join our Discord server