Skip to main content
Glama
Host Process & Sub-Agent Governor

Host Process & Sub-Agent Governor

by jasonroject

governor_status

Inspect current governor state to view active sub-agents per model, queue depths, and running host background processes, with an optional model filter.

Instructions

Inspect the current governor state: active sub-agents per model, queue depths, and running host background processes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "governor_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelIdNoOptional model filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full behavioral burden. It implies read-only inspection and tells the agent what categories of state are reported, but says nothing about freshness, cost, permissions, or whether the snapshot is global versus scoped.

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?

One sentence, front-loaded with the verb and resource, followed by a compact enumeration of what is reported. There is no filler and nothing redundant.

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?

With no output schema, the description does the necessary work of naming the returned state categories. For a one-optional-parameter status tool that is nearly sufficient; only the effect of the modelId filter on the returned shape is unaddressed.

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

Parameters3/5

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

Schema description coverage is 100%, so the single optional 'modelId' parameter is already documented in the schema; baseline 3 applies. The phrase 'per model' hints that results are broken out by model, but the description never explains what omitting modelId does.

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?

States a specific verb ('Inspect') and resource ('governor state'), then enumerates the observable contents: active sub-agents per model, queue depths, and host background processes. That distinguishes it from mutating siblings like governor_acquire_slot or governor_release_slot, though it never names a sibling explicitly.

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 word 'Inspect' and 'current state' imply a read-only observation use case, which is enough to infer the general situation. It gives no explicit when-to-use guidance, no prerequisites, and does not say how it differs from governor_diagnose or host_exec_status.

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