Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Get repository settings

repo_settings_get
Read-onlyIdempotent

Fetch repository-level Auto patch, Auto review, Auto land, merge queue, and overdrive settings for one or all connected repositories to see which values are set or inherit account defaults.

Instructions

Read the repository-level Auto patch, Auto review, Auto land, merge queue (merge_queue_batch_enabled, merge_queue_batch_size, merge_queue_lands_alone_paths) and merge queue overdrive values for the repositories connected to this account. auto_patch_enabled, auto_review_enabled, auto_land_default, merge_queue_batch_enabled and merge_queue_overdrive are true, false, or null; merge_queue_batch_size is a whole number or null; merge_queue_lands_alone_paths is a list of path patterns or null. null means not set, so the account setting applies. Auto patch and Auto review precedence is the stack override (stack_set), then the repository value, then the account setting (settings_get). The Auto land repository value only seeds new stacks at adoption; it does not override an existing stack. merge_queue_overdrive is the repository value over the account default; while it resolves on, that repository batches up to 10 queued pull requests. issue_review_enabled is true, false, or null: the repository value for Vortex issue reviews over the account default (settings_get issue_review_enabled). issue_auto_review_enabled is true, false, or null the same way: while issue reviews are on, true reviews every new issue and reply, and false reviews only when a comment tags @mergestorm-vortex. Pass repo as owner/repo for one repository, or omit it for all.

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

Input Schema

NameRequiredDescriptionDefault
repoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), yet the description goes well beyond them: it explains that null means "not set, so the account setting applies," spells out the three-level precedence for Auto patch/review, and clarifies that the Auto land repository value only seeds new stacks rather than overriding existing ones. It also discloses concrete effects such as merge queue overdrive resolving to batches of up to 10 queued PRs and issue_auto_review_enabled controlling whether every issue is reviewed or only tagged ones.

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 is front-loaded, but the remainder is a single dense ~150-word paragraph that mixes field types, precedence rules, and per-field semantics with no sentence-level structure. Most content earns its place, but it would read far better as a short lead plus a list.

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?

With no output schema, the description takes on the burden of describing return values and does so field-by-field, including types and null semantics, which is genuinely complete. What it omits is the shape of the response envelope (e.g., how per-repository values are keyed when repo is omitted), the one detail an agent would still need to parse the result.

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% and the only parameter is undocumented in the schema, so the description must carry it — and it does, specifying the owner/repo format and the omit-for-all default. It stops short of mentioning any validation constraints (e.g., minimum length), but the essential meaning is conveyed.

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?

The opening sentence uses a specific verb ("Read") on a specific resource (repository-level Auto patch, Auto review, Auto land, merge queue and overdrive values) scoped to "the repositories connected to this account." It also implicitly distinguishes itself from the account-level sibling settings_get and from the setter repo_settings_set by naming settings_get as the fallback layer.

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 final sentence gives concrete invocation guidance ("Pass repo as owner/repo for one repository, or omit it for all"), which is real when-to-use direction. The precedence chain (stack_set then repository then settings_get) hints that account-level reads belong to settings_get, but no explicit "use settings_get instead when..." routing or exclusion is stated, so guidance is implied rather than declared.

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