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

Host Process & Sub-Agent Governor

by jasonroject

host_exec_stop

Stops a running background host process and terminates its entire child process tree, with an optional force kill for stubborn processes.

Instructions

Stop or kill a running background host process and its entire child process tree.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "processId": "<processId>"
    },
    "name": "host_exec_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoWhether to force kill (SIGKILL/taskkill /F). Defaults to false.
processIdYesProcess ID to terminate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 that the entire child process tree is affected, but it does not explain irreversibility, permissions, signal handling, or what happens if the process is already stopped.

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?

It is a single, front-loaded sentence with no wasted wording and immediately communicates the tool's scope.

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 simple two-parameter termination tool with full schema coverage, the description is mostly complete: it names the resource and the child-tree scope. Minor gaps remain around safety/profile details, but nothing critical to invocation is missing.

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 both parameters are already documented in the schema. The description adds no meaning beyond the schema, such as clarifying the effect of force versus non-force termination.

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 states a specific verb (stop/kill) and resource (running background host process and its entire child process tree), which clearly distinguishes it from siblings such as host_exec_start, host_exec_status, and host_exec_logs.

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 description implies when to use the tool by naming the operation against a running process, but it does not explicitly say when to prefer it over alternatives, when not to use it, or when to choose graceful stop versus force kill.

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