Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Update repository settings

repo_settings_set
Destructive

Set repository-level Auto patch, Auto review, Auto land, issue review, and merge queue settings, or clear an override to inherit account defaults; stored values are returned.

Instructions

Set Auto patch (Cyclone), Auto review (Vortex), the Auto land default, or the merge queue settings (merge_queue_batch, merge_queue_batch_size, merge_queue_lands_alone_paths, merge_queue_overdrive) for every stack and pull request in one repository connected to this account, and return the stored result. A value sets the repository value; null clears it so the account setting applies again. A stack override (stack_set) still wins for that stack. auto_patch and auto_review apply to open stacks without an override from their next decision; nothing is cancelled or re-queued. auto_land only seeds new stacks. merge_queue_lands_alone_paths is a list of folder prefixes or globs; a queued pull request that changes a matching file is never batched with others, and an empty list keeps only the built-in rule that a stack with more than one open pull request lands alone. merge_queue_overdrive true makes that repository batch up to 10 queued pull requests, even with batching off; false turns overdrive off for that repository whatever the account default is, and null clears the repository value so the account default (settings_get merge_queue_overdrive) applies again. issue_review true or false turns Vortex issue reviews on or off for that repository whatever the account default is; null clears the repository value so the account default (settings_get issue_review_enabled) applies again. issue_auto_review false makes those reviews run only when a comment tags @mergestorm-vortex (opening a PR then needs no issue approval), true reviews every new issue and reply, and null inherits the account default (settings_get issue_auto_review_enabled). Only the account that connected the repository can change it. Never changes account settings.

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": {
      "repo": "<repo>"
    },
    "name": "repo_settings_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYes
auto_landNo
auto_patchNo
auto_reviewNo
issue_reviewNo
issue_auto_reviewNo
merge_queue_batchNo
merge_queue_overdriveNo
merge_queue_batch_sizeNo
merge_queue_lands_alone_pathsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

A4.4/5.0
Behavior5/5

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

Far exceeds the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=false): it discloses that auto_patch/auto_review apply from the next decision and nothing is cancelled or re-queued, that auto_land only seeds new stacks, that null clears and reverts to account defaults, and that only the connecting account can change the repository. This adds real behavioral context the annotations cannot convey.

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 main verb and setting list are front-loaded, but the body is a dense wall of text with repeated 'null clears the repository value so the account default applies' phrasing across several parameters. Most sentences carry information, but the repetition and lack of paragraphing make it harder to scan than necessary.

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 10-parameter mutation with no output schema, it covers effects, inheritance rules, and authorization well. It is only slightly incomplete: merge_queue_batch_size semantics are missing and 'return the stored result' does not describe the response shape.

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 0%, so the description must carry the burden and largely does: it explains tri-state null semantics, glob/folder-prefix behavior for merge_queue_lands_alone_paths including the built-in single-PR rule, overdrive's batch-of-10 effect, and the three-way null/true/false meaning for issue_auto_review. The notable gap is merge_queue_batch_size, which is listed but never explained.

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 ('Set') and enumerates the exact settings it touches (auto patch, auto review, auto land default, merge queue settings) scoped to 'one repository connected to this account'. It also distinguishes itself from siblings by noting a stack override (stack_set) still wins and that it never changes account settings.

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 clear usage context: a value sets the repository value, null clears it so the account setting applies again, and stack_set overrides still take precedence. It names settings_get for account defaults but does not explicitly say to use repo_settings_get to read current repository values instead of this tool, so routing is good but not airtight.

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