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

Host Process & Sub-Agent Governor

by jasonroject

governor_diagnose

Run deep diagnostics on the host execution environment, active sub-agent locks, and resource utilization to identify concurrency bottlenecks and environment issues.

Instructions

Run deep diagnostics on the host execution environment, active sub-agent locks, and resource utilization.

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_diagnose"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the inspection scope (host environment, sub-agent locks, resource utilization), which is real behavioral context, but it omits whether the operation is read-only, how expensive or slow it is, and whether it can block on held locks.

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?

A single front-loaded sentence that names the action first and then the targets, with no filler. Nothing further is needed for length, though the sentence could have carried one more clause of guidance at no structural cost.

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

Completeness3/5

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

With zero parameters and no output schema, the main open question is what the diagnostics report and whether it is safe/cheap to call. The description establishes what is inspected but not what comes back or how it relates to governor_status, leaving a meaningful gap.

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 takes zero parameters, so there is no parameter meaning to convey; the baseline for a no-param tool applies. The description correctly implies no inputs are required to run diagnostics.

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 names a specific action ("Run deep diagnostics") and enumerates the exact targets: host execution environment, active sub-agent locks, and resource utilization. This makes the tool's scope concrete and distinguishable from a plain status check, though it never names a sibling to contrast with.

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 "deep" implies a heavier, investigative operation than a routine status poll, which hints at when to reach for it. However, there is no explicit when-to-use, no when-not-to-use, and no reference to governor_status as the lighter alternative.

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