Skip to main content
Glama
po4erk91

Thread Keeper

by po4erk91
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

spawn_budget_status

Read-only

Check current spawn-budget usage: cap, used, free, and per-task RSS, to determine if another spawn can be admitted.

Instructions

Report current spawn-budget usage: cap, used, free, plus per-running-task RSS. Used to decide whether another spawn() will be admitted.

Values come from the budget daemon (refreshes every SPAWN_BUDGET_POLL_S seconds via ps). Just-spawned tasks show their initial estimate until the daemon catches up. Visible (pid=0, Terminal-launched) spawns are tracked too: the daemon resolves their live pid from the forced session-id and measures real RSS, and reaps a row whose cid never resolves past SPAWN_VISIBLE_TTL_S (#64).

Returns structuredContent (SpawnBudgetStatus) plus the legacy text block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksNo
cap_mbNo
poll_sNo
enabledNo
free_mbNo
runningNo
used_mbNo
tokens_24hNo
tokens_freeNo
cost_usd_24hNo
token_budgetNo
cost_free_usdNo
cost_budget_usdNo
cost_budget_enabledNo
token_budget_enabledNo

Schema Changelog

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

  1. Changed20 schema fields changedv0.14.0
    • addedOutput schema / $defs
      Added value: +{
+  "SpawnTaskRss": {
+    "additionalProperties": true,
+    "properties": {
+      "age_s": {
+        "default": 0,
+        "title": "Age S",
+        "type": "integer"
+      },
+      "cid": {
+        "default": "-",
+        "title": "Cid",
+        "type": "string"
+      },
+      "id": {
+        "title": "Id",
+        "type": "string"
+      },
+      "pid": {
+        "default": 0,
+        "title": "Pid",
+        "type": "integer"
+      },
+      "prompt": {
+        "default": "",
+        "title": "Prompt",
+        "type": "string"
+      },
+      "rss_mb": {
+        "default": 0,
+        "title": "Rss Mb",
+        "type": "integer"
+      }
+    },
+    "required": [
+      "id"
+    ],
+    "title": "SpawnTaskRss",
+    "type": "object"
+  }
+}
    • addedOutput schema / description
      Added value: +"Spawn-budget usage: cap, used, free, plus per-running-task RSS."
    • addedOutput schema / properties / cap_mb
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Cap Mb"
+}
    • addedOutput schema / properties / cost_budget_enabled
      Added value: +{
+  "default": false,
+  "title": "Cost Budget Enabled",
+  "type": "boolean"
+}
    • addedOutput schema / properties / cost_budget_usd
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Cost Budget Usd"
+}
    • addedOutput schema / properties / cost_free_usd
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Cost Free Usd"
+}
    • addedOutput schema / properties / cost_usd_24h
      Added value: +{
+  "default": 0,
+  "title": "Cost Usd 24H",
+  "type": "number"
+}
    • addedOutput schema / properties / enabled
      Added value: +{
+  "default": true,
+  "title": "Enabled",
+  "type": "boolean"
+}
    • addedOutput schema / properties / free_mb
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Free Mb"
+}
    • addedOutput schema / properties / poll_s
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Poll S"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "title": "Result",
-  "type": "string"
-}
    • addedOutput schema / properties / running
      Added value: +{
+  "default": 0,
+  "title": "Running",
+  "type": "integer"
+}
    • addedOutput schema / properties / tasks
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/SpawnTaskRss"
+  },
+  "title": "Tasks",
+  "type": "array"
+}
    • addedOutput schema / properties / token_budget
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Token Budget"
+}
    • addedOutput schema / properties / token_budget_enabled
      Added value: +{
+  "default": false,
+  "title": "Token Budget Enabled",
+  "type": "boolean"
+}
    • addedOutput schema / properties / tokens_24h
      Added value: +{
+  "default": 0,
+  "title": "Tokens 24H",
+  "type": "integer"
+}
    • addedOutput schema / properties / tokens_free
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Tokens Free"
+}
    • addedOutput schema / properties / used_mb
      Added value: +{
+  "default": 0,
+  "title": "Used Mb",
+  "type": "integer"
+}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • changedOutput schema / title
      Previous value: -"spawn_budget_statusOutput"New value: +"SpawnBudgetStatus"
  2. First observedv0.13.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description adds value by detailing data source (budget daemon, ps, polling interval), staleness behavior, and handling of visible spawns. No contradictions; the description enriches understanding of the tool's behavior.

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 two paragraphs: first succinctly states purpose and output; second adds technical details. It is front-loaded and contains no redundant sentences. Slightly dense with acronyms and references, but overall 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 read-only status tool with no parameters, the description is exceptionally complete. It covers purpose, output structure (structured content and legacy text), data source, refresh timing, edge cases (just-spawned tasks, visible spawns), and even references relevant constants. No gaps.

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 has zero parameters, so schema coverage is 100%. The description does not need to add parameter details. Baseline for 0 params is 4, and no additional information is required.

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 explicitly states the tool reports current spawn-budget usage including cap, used, free, and per-task RSS, for deciding whether another spawn() will be admitted. It clearly specifies the verb 'report' and the resource, and distinguishes from siblings like spawn_budget_set and 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 Guidelines4/5

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

The description indicates when to use ('to decide whether another spawn() will be admitted') and provides context on timing (daemon refresh, initial estimates for just-spawned tasks). It does not explicitly state when not to use or name alternatives, but the context is clear given sibling tools.

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

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