Skip to main content
Glama

update_config

Destructive

Replace a repository's MergeQueue YAML configuration by submitting the complete updated file after retrieving and editing the current config; supports parallel merge settings.

Instructions

Replace a repo's MergeQueue YAML config. Call get_config first, edit only what was asked, send the whole file. Parallel mode: merge_rules.merge_mode.type: parallel + merge_mode.parallel_mode.max_parallel_builds / batch_size.

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": {
      "yaml_config": "<yaml_config>"
    },
    "name": "update_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoGitHub org. Optional if repo is 'org/name'.
repoNoGitHub repo name or 'org/name'.
yaml_configYesThe FULL new aviator config YAML (replaces the current one).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description usefully explains *why*: the entire file is replaced, so anything omitted is lost — that is the key destruction detail an agent needs. It does not cover validation failure behavior or what happens to the queue if invalid YAML is submitted.

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?

Three short sentences, front-loaded with the action and the destructive semantics before the optional key reference. The final sentence is telegraphic and slightly cryptic, but it carries specific configuration content rather than filler.

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 destructive whole-file replacement with no output schema, the description supplies the read-then-write workflow, the replacement semantics, and a pointer to the tricky parallel-mode keys. Remaining gap is error/validation behavior and whether the change is applied atomically.

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?

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema by naming the exact YAML keys needed to configure parallel mode (merge_rules.merge_mode.type, max_parallel_builds, batch_size). That is payload-level guidance the schema's 'FULL new aviator config YAML' string does not provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Replace') and resource ('a repo's MergeQueue YAML config'), and the 'call get_config first' clause immediately distinguishes it from the read counterpart among siblings. Full-replacement scope is unambiguous.

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

Usage Guidelines4/5

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

Gives a concrete workflow: read with get_config, edit only what was asked, then send the whole file — this is real when-to-use guidance plus a prerequisite. It stops short of explicit when-not-to-use conditions (e.g. don't use for reads or partial patches), but the alternative is named.

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