Skip to main content
Glama

set_agent_limits

DestructiveIdempotent

Sets the maximum number of tasks an operator's agent can run concurrently on the runner; requires the agent's own key and the operator's 'Can manage My Runner' permission.

Instructions

Set how many tasks one of your operator's agents may run at once on the runner (max_concurrent_tasks). Works with the agent's own key only while its operator keeps "Can manage My Runner" on; otherwise the server's 403 is returned word for word.

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": {
      "agent_id": "<agent_id>",
      "max_concurrent_tasks": "<max_concurrent_tasks>"
    },
    "name": "set_agent_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesUUID of the operator's agent whose limit changes.
max_concurrent_tasksYesMaximum tasks the agent runs in parallel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered; the description adds genuinely new behavior: the authorization model (agent key plus operator's 'Can manage My Runner' toggle) and the failure mode (server 403 surfaced verbatim rather than swallowed). It stops short of saying whether lowering the limit affects already-running tasks or whether the change takes effect immediately, which matters for a destructive mutation.

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?

Two tight sentences, with the operation stated first and the permission precondition second, so it is well front-loaded. The closing phrase 'returned word for word' is slightly colloquial but conveys a real behavior, so there is little waste.

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 two-parameter mutation with full schema coverage and no output schema, the definition supplies what an agent needs: what is changed, whose key is required, and what error to expect. The remaining gap — effect on in-flight tasks and whether the limit is applied instantly — is real but modest given the tool's simplicity.

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 input schema, and the description mainly restates max_concurrent_tasks. The phrase 'on the runner' adds a little scope information — concurrency is enforced at the runner rather than at task admission — but this is marginal, so 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?

The description gives a specific verb and resource ('Set how many tasks one of your operator's agents may run at once on the runner') and even names the underlying field (max_concurrent_tasks), so the effect is unambiguous. It does not contrast itself with any sibling, but none of the named siblings obviously overlaps, so the resource naming does most of the disambiguation work.

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?

It states a real precondition — the agent's own key works only while its operator keeps 'Can manage My Runner' enabled — which tells the agent when the call is viable. It says nothing about when to choose this over an operator-wide or runner-wide alternative, and gives no guidance on prerequisites to verify beforehand beyond the permission flag.

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