Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Update settings

settings_set
Destructive

Update writable account settings via the Bearer API and return stored values, including merge queue batching, auto-land settle timing, issue review defaults, and related workflow options.

Instructions

Update writable Bearer /api/v1/settings values and return the stored result. At least one key is required. auto_land_settle_seconds is a whole number of seconds from 15 through 300; it applies to settle clocks that start after the write. merge_queue_batch_enabled turns merge queue batching on or off for the account, merge_queue_batch_size is a whole number from 2 through 10, merge_queue_lands_alone_paths is the list of folder prefixes or globs whose changed files keep a pull request out of a batch, and merge_queue_overdrive is the account default for overdrive: while it resolves on, a repository batches up to 10 queued pull requests, even with batching off, without changing merge_queue_batch_size, and it stays on until turned off (repo_settings_set overrides each of these per repository). issue_review_enabled is the account default for Vortex issue reviews; repo_settings_set issue_review overrides it per repository. issue_auto_review_enabled false makes them run only when a comment tags @mergestorm-vortex; repo_settings_set issue_auto_review overrides it per repository. cyclone_connected and github_connected are read-only and cannot be set.

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

Input Schema

NameRequiredDescriptionDefault
github_connectedNo
auto_land_defaultNo
cyclone_connectedNo
auto_patch_enabledNo
ignored_bot_loginsNo
auto_fix_ci_enabledNo
auto_review_enabledNo
issue_review_enabledNo
merge_queue_overdriveNo
repo_overview_enabledNo
vortex_bot_skip_checkNo
vortex_findings_checkNo
merge_queue_batch_sizeNo
cyclone_skip_ci_enabledNo
auto_land_settle_secondsNo
issue_auto_review_enabledNo
merge_queue_batch_enabledNo
cyclone_patch_failure_checkNo
vortex_show_thinking_tracesNo
vortex_auto_overflow_enabledNo
merge_queue_lands_alone_pathsNo
auto_resolve_conflicts_enabledNo
vortex_seam_specialist_enabledNo
vortex_skip_all_clear_commentsNo
cyclone_patch_unverified_languagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations it discloses real behavioral nuance: auto_land_settle_seconds only affects settle clocks starting after the write, merge_queue_overdrive persists 'until turned off' and overrides batching-off behavior, and two keys are rejected outright. It does not explain what happens to the 20+ unmentioned settings (are they preserved or cleared?) nor what makes this destructive despite destructiveHint=true.

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 purpose and the at-least-one-key constraint are correctly front-loaded, but the body is a single run-on sentence enumerating eight-plus parameters with embedded clauses. It is dense rather than wasteful, yet the merge-queue paragraph is hard to scan and would read better as a short list.

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?

For a 25-parameter, destructive, open-world mutation with no output schema, the description covers the highest-risk knobs and the read-only exception, but omits whether a partial update preserves untouched settings and says nothing about permissions, failure modes, or confirmation requirements.

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 25 parameters, so the description carries the full burden; it defines roughly a third of them in depth (settle seconds range 15-300, batch size 2-10, lands-alone paths as folder prefixes or globs, overdrive semantics, issue review toggles). The remaining parameters (auto_patch_enabled, ignored_bot_logins, the vortex_*_check enums, cyclone_* flags, etc.) get no meaning beyond their names and enum values.

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 and resource ('Update writable Bearer /api/v1/settings values') plus the return ('return the stored result'). It also implicitly separates this account-level tool from the sibling repo_settings_set by repeatedly noting per-repository overrides.

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?

It gives a hard precondition ('At least one key is required') and rules out read-only inputs ('cyclone_connected and github_connected are read-only and cannot be set'), and it points at repo_settings_set for per-repository overrides. It does not explicitly say to call settings_get first or what to do for settings not listed, so it falls short of full when/when-not guidance.

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