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

Host Process & Sub-Agent Governor

by jasonroject

governor_release_slot

Release a previously acquired sub-agent slot to unblock queued sub-agents waiting for that model. Frees concurrency capacity so pending tasks can start.

Instructions

Release a previously acquired sub-agent slot, unblocking pending queued sub-agents for that model.

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": {
      "leaseId": "<leaseId>"
    },
    "name": "governor_release_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
leaseIdYesThe lease ID returned by governor_acquire_slot.

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 supplied, so the description carries the full behavioral burden. It does disclose a meaningful side effect — queued sub-agents for that model become unblocked — but says nothing about idempotency, behavior with an expired/unknown leaseId, error responses, or permissions, which are the details an agent most needs for a lifecycle-mutating call.

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 action and followed by the consequence; there is no filler or redundancy.

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?

For a simple one-parameter lifecycle tool this covers purpose and effect adequately, and no output schema exists so return values need not be explained. However, with zero annotations the description should say more about failure modes and idempotency to be fully sufficient for a slot-release operation.

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% and the single parameter is documented as 'The lease ID returned by governor_acquire_slot,' which already conveys the source and format. The description adds no further parameter meaning, so the baseline 3 applies.

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 ('Release') and resource ('a previously acquired sub-agent slot') and adds the resulting effect ('unblocking pending queued sub-agents'). The phrase 'previously acquired' implicitly pairs it with governor_acquire_slot, but it never names that sibling explicitly to harden the distinction.

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 implied rather than stated: an agent can infer it should call this after holding a lease from governor_acquire_slot. There is no explicit when-to-call trigger, no note about whether release is required or optional, and no mention of what happens if a lease is never released.

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