Skip to main content
Glama

Configure resource governor

resource_governor_configure
Destructive

Enable or disable automatic admission throttling for heavy shell/build work based on CPU, memory, and concurrency limits to prevent overload.

Instructions

Enable/disable automatic admission throttling for heavy shell/build work based on CPU, memory and concurrency.

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": "resource_governor_configure"
  }
}

Input Schema

NameRequiredDescriptionDefault
pollMsNo
enabledNo
deviceIdNo
deviceNameNo
minFreeMemoryBytesNo
maxSystemCpuPercentNo
maxConcurrentHeavyOpsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already disclose readOnlyHint=false and destructiveHint=true, so the mutation risk profile is covered. The description adds domain context about what is being throttled and on what signals, but says nothing about persistence, effect on in-flight operations, or what happens when disabled.

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?

A single front-loaded sentence with the action first and zero filler. Nothing needs to be moved or cut.

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

Completeness2/5

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

For a destructive 7-parameter configuration tool with 0% schema description coverage and no output schema, the definition is too thin: parameters, units, defaults, and persistence behavior are all absent, leaving the agent under-equipped to call it correctly.

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

Parameters2/5

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

Schema coverage is 0% across 7 parameters. The description gestures at the domain (CPU, memory, concurrency) but does not map to any specific field such as pollMs, deviceId, minFreeMemoryBytes, or the max* thresholds, leaving their meaning and units unexplained.

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 action (enable/disable) on a specific mechanism (automatic admission throttling) and names the triggering dimensions (CPU, memory, concurrency). It is clearly a configuration tool, distinguishable in intent from resource_governor_status, though it never names that sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no mention of the related resource_governor_status or watch tools. The agent must infer the operational context (managing heavy build/shell load) entirely on its own.

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

Deploy Server

Other Tools