Thread Keeper

Overview Schema Related Servers Score Discussions

agent_status

Read-only

Get a snapshot of each autonomous learning loop, including current state, backlog, last pass, and RSS. Use it to monitor agent progress and identify stalled tasks.

Instructions

Show autonomous learning loops with state, backlog, last pass, and RSS.

Set json_output=True for the same stable shape used by the menu-bar app. Always returns structuredContent (AgentStatusSnapshot); the text block is the JSON dump when json_output else the formatted summary.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`refresh`	No
`json_output`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`loops`	No
`agents`	No
`generated_at`	No
`total_rss_kb`	No
`total_rss_mb`	No
`github_budget`	No
`running_count`	No
`recent_results`	No
`timed_out_count`	No
`ready_loop_count`	No
`enabled_loop_count`	No
`running_loop_count`	No

Schema Changelog

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

Changed1 schema field changedv0.17.0Aug 28, 2026

addedOutput schema / properties / github_budget

Added value: +{
+  "additionalProperties": true,
+  "title": "Github Budget",
+  "type": "object"
+}

Changed16 schema fields changedv0.14.0Jun 25, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

addedOutput schema / description

Added value: +"Autonomous learning loops + running children (JSON-ready snapshot)."

addedOutput schema / properties / agents

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "title": "Agents",
+  "type": "array"
+}

addedOutput schema / properties / enabled_loop_count

Added value: +{
+  "default": 0,
+  "title": "Enabled Loop Count",
+  "type": "integer"
+}

addedOutput schema / properties / generated_at

Added value: +{
+  "default": 0,
+  "title": "Generated At",
+  "type": "integer"
+}

addedOutput schema / properties / loops

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "title": "Loops",
+  "type": "array"
+}

addedOutput schema / properties / ready_loop_count

Added value: +{
+  "default": 0,
+  "title": "Ready Loop Count",
+  "type": "integer"
+}

addedOutput schema / properties / recent_results

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "title": "Recent Results",
+  "type": "array"
+}

removedOutput schema / properties / result

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

addedOutput schema / properties / running_count

Added value: +{
+  "default": 0,
+  "title": "Running Count",
+  "type": "integer"
+}

addedOutput schema / properties / running_loop_count

Added value: +{
+  "default": 0,
+  "title": "Running Loop Count",
+  "type": "integer"
+}

addedOutput schema / properties / timed_out_count

Added value: +{
+  "default": 0,
+  "title": "Timed Out Count",
+  "type": "integer"
+}

addedOutput schema / properties / total_rss_kb

Added value: +{
+  "default": 0,
+  "title": "Total Rss Kb",
+  "type": "integer"
+}

addedOutput schema / properties / total_rss_mb

Added value: +{
+  "default": 0,
+  "title": "Total Rss Mb",
+  "type": "integer"
+}

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

changedOutput schema / title

Previous value: -"agent_statusOutput"New value: +"AgentStatusSnapshot"

First observedv0.13.2Jun 17, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses that the tool always returns structuredContent with an AgentStatusSnapshot, and explains how the text block changes with json_output. This adds meaningful behavioral context without contradicting the read-only annotation.

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?

Three tight sentences with no filler. The primary purpose is front-loaded, and the only additional sentence explains return behavior and the json_output switch.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the readOnlyHint, presence of an output schema, and only two optional boolean parameters, the description covers most of what an agent needs: purpose, return shape, and output formatting. The undocumented refresh parameter is the main remaining gap.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden for both parameters. It explains json_output well, but refresh is left completely undocumented, leaving an agent to guess whether it triggers a refresh, controls caching, or has side effects.

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 says specifically to 'Show autonomous learning loops' and enumerates the content fields: state, backlog, last pass, and RSS. This is a clear verb+resource statement, though it does not explicitly differentiate from sibling status tools like live_status or spawn_status.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives. The json_output instruction is useful for output formatting but does not help the agent decide between agent_status and sibling status/health tools, and no exclusions or prerequisites are stated.

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