Skip to main content
Glama

set_crew_settings

Saves a person’s chosen crew settings, changing only supplied values and clearing named overrides to fall back to team defaults. Controls autonomy, pacing, idle wake, and Docker cleanup.

Instructions

Save the crew's settings the person chose (only the ones given change). They are saved for that person; on a single-user cell they are the cell's. A personal autonomy or challenger can be as strict as the team's or stricter, not looser. clear names settings to unset, so a person's own fall back to the team's. Only the person's own session or the orchestrator may. idle_wake true has the watch wake idle stations when they have work, instead of each ticking on its own. pace true slows the crew before the plan's limits are hit. docker_cleanup false stops the daily Docker cleanup; docker_keep (image names, * as a wildcard) replaces the list of images it never removes.

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

Input Schema

NameRequiredDescriptionDefault
paceNo
clearNo
autonomyNo
releaserNo
idle_wakeNo
challengerNo
docker_keepNo
builders_maxNo
prod_patternNo
claude_updateNo
docker_cleanupNo
release_profileNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses partial-update semantics, per-person vs single-user-cell scoping of the saved values, the permission requirement, and the inheritance constraint that personal autonomy/challenger can be stricter but not looser than the team's. It does not describe validation failures or what the save returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and front-loaded with scope and permissions before per-parameter notes, with no filler. However, telegraphic fragments like 'Only the person's own session or the orchestrator may.' lack the verb and object, making the sentence ambiguous on a first read.

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?

Output schema exists so return values need not be explained, and the description covers the hard parts of a settings mutation. With 12 parameters at zero schema coverage and no annotations, the five unexplained parameters leave a meaningful gap for an agent deciding what to pass.

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 0% across 12 parameters, and the description explains the meaning of pace, idle_wake, docker_cleanup, docker_keep, clear, autonomy, and challenger behaviorally. Five parameters (releaser, builders_max, prod_pattern, claude_update, release_profile) get no mention at all, leaving the agent to guess.

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?

'Save the crew's settings the person chose' names a specific verb and resource, and 'only the ones given change' clarifies merge semantics. It implicitly contrasts with the get_crew_settings sibling but never states the distinction 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?

The description gives a strong usage rule for `clear` (unset so the person's own fall back to the team's) and an authorization constraint ('Only the person's own session or the orchestrator may'), which tells the agent who can call it. It does not say when to prefer this over related settings tools or what happens on failure.

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