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

Host Process & Sub-Agent Governor

by jasonroject

host_exec_status

Retrieve status, exit code, state history, and runtime info for a background process, or list all managed processes when no ID is supplied.

Instructions

Get status, exit code, state history, and runtime info of a background process, or list all running 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": "host_exec_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
processIdNoProcess ID to inspect. If omitted, lists all managed processes.

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 usefully discloses the fields returned (exit code, state history, runtime info) and the dual read mode, implying a non-mutating operation, but says nothing about permissions, behavior for unknown/finished process IDs, or whether history is truncated.

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 efficient sentence with the richer inspection mode front-loaded and the enumeration mode trailing. Only minor redundancy between 'status' and 'state history' and the running/managed wording mismatch keep it from a 5.

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?

For a one-optional-parameter tool with no output schema, the description covers both modes and enumerates the kinds of information returned, which is what an agent needs to decide and call. Missing only edge-case behavior such as invalid IDs or non-running processes.

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 coverage is 100% and the processId description already explains the omission behavior, so the description adds little beyond restating the two modes. It introduces a small inconsistency by saying 'running processes' where the schema says 'all managed processes'.

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 gives a specific verb and resource ('Get status, exit code, state history, and runtime info of a background process') and also names the fallback mode ('list all running processes'). An agent can tell this apart from host_exec_logs or host_exec_start by the reported fields, though no sibling is named 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?

Usage is only implied: the 'or list all' clause hints that omitting the process ID triggers enumeration, and that behavior is confirmed in the schema. There is no explicit guidance on when to prefer this over host_exec_logs or governor_status, and no stated prerequisites.

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