Skip to main content
Glama

get_crew_settings

Read the crew's project settings and defaults—autonomy, releaser, builder limits, Docker cleanup, and idle pacing—to adapt your workflow without guessing.

Instructions

The tares-factory crew's settings for every project: autonomy (L3-review: the person approves each merge; L4-ship: Tares merges after the review gate passes and CI is green), releaser (whether the crew runs a releaser; without one a ticket ends at merged), release_profile, prod_pattern (what counts as prod), challenger (builders run the Codex challenger), builders_max, claude_update (whether the watch moves stations onto a new Claude Code; on unless false). Unset ones are null: ask the person, one at a time, with a recommendation. These are the caller's own settings where they have set one, else the team's default. kit.frozen is null while the crew follows the plugin checkout, else when and by whom the person froze it (tares factory crew freeze): the watch then moves no station onto a newer kit. Read only here; the person freezes and unfreezes from the CLI. idle_wake (null or false: off): when true the factory's watch wakes you with a message when you have work and holds your liveness tick, so you arm no schedule of your own. pace (null or false: off): when true the watch slows the crew before the plan's limits: no new builders, a 45-minute tick, and builders wait near the 5-hour limit; its notes to you say what to do. docker_cleanup (on unless false): once a day the watch removes Docker's leftovers on the crew machine (stopped containers, old build cache, images unused for 7 days; never volumes), and a heavy command cleans up first when the disk is low. docker_keep lists image names 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": "get_crew_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and largely meets it: it declares the tool read-only, states that freeze/unfreeze happens only via the CLI, explains the caller-vs-team-default resolution, and discloses the downstream behavior of settings like idle_wake, pace, and docker_cleanup (what the watch does, what is never deleted). It omits nothing critical for a zero-parameter read, though it says nothing about permissions or failure modes.

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?

The first sentence is a long run-on that buries several field definitions mid-clause, so front-loading is weak. Much of the field-by-field detail likely duplicates the output schema, and roughly 250 words for a zero-argument getter is heavy — though nearly every clause does convey semantics an agent could act on.

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?

An output schema exists, so the description need not explain return values, yet it goes further and documents each field's meaning plus the null/default conventions that the schema alone would not convey. The remaining gap is the absence of any explicit statement of when this call is warranted relative to sibling tools.

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

Parameters4/5

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

The input schema has zero properties, so there are no parameters whose meaning needs elaboration. Baseline of 4 applies; the description correctly spends its space on return-value semantics instead.

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 opening identifies the resource precisely ("the tares-factory crew's settings for every project") and enumerates the fields it covers, so an agent knows exactly what data comes back. However, it never uses an explicit verb like "returns" or "reads" — the getter nature is inferred from the name and the later phrase "Read only here". It also distinguishes itself from a write path by pointing mutation to the CLI, though it never names the set_crew_settings sibling.

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?

There is no explicit statement of when to call this versus alternatives such as crew_projects or how_is_project; usage is only implied (read settings before acting on autonomy, release, or watch behavior). It does give strong post-call guidance — unset fields are null and should be asked about "one at a time, with a recommendation" — and routes mutation to the CLI, which partially compensates.

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