Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Get settings

settings_get
Read-onlyIdempotent

Retrieve account-level MergeStorm settings such as Auto land timing, merge queue batching, issue review defaults, Cyclone connection, and stacks readiness before changing repository behavior.

Instructions

Read the Bearer /api/v1/settings toggles, including auto_patch_enabled, auto_land_settle_seconds (how long Auto land waits before queueing), merge_queue_batch_enabled and merge_queue_batch_size (whether the merge queue tests several pull requests on one CI run, and how many), merge_queue_overdrive (the account default for overdrive: the merge queue batches up to 10 queued pull requests per repository; repo_settings_set overrides it per repository), issue_review_enabled (the account default for Vortex issue reviews; repo_settings_set overrides it per repository), issue_auto_review_enabled (the account default for whether those reviews run on every issue or only when a comment tags @mergestorm-vortex), cyclone_connected (the Cyclone auto-patch App), and stacks_ready (whether stacks, the merge queue and Auto land can run for this account, which needs Mergestorm Surge).

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds substantive context beyond that: which fields are account defaults overridable per repo, that stacks_ready depends on a Mergestorm Surge subscription, and what auto_land_settle_seconds and the merge-queue batch fields operationally mean. It does not describe the response envelope or failure behavior, which keeps it below a 5.

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 content is relevant, but it is delivered as a single run-on sentence with deeply nested parentheticals, so it is not front-loaded and is hard to scan for a specific field. Several clauses (e.g. the 10-pull-request overdrive detail) are dense enough to slow comprehension.

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?

There is no output schema, so the description carries the burden of explaining what comes back, and it does enumerate every documented field with meaning. It stops short of stating the response shape (object vs. keyed list) or behavior on missing/disabled settings, leaving a small gap for a zero-param read tool.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The lengthy field explanations describe return values rather than inputs, which is useful but not a parameter-semantics contribution.

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 ('Read') and resource ('/api/v1/settings toggles') and then enumerates the exact fields returned, so an agent knows precisely what this returns. It also names repo_settings_set as the per-repository override for two of those fields, which distinguishes it from the repo-scoped 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?

Usage is only implied: the mention that repo_settings_set 'overrides it per repository' hints at the relationship between account-level and repo-level settings, but there is no explicit 'call this when...' or 'use repo_settings_get instead if...' guidance. An agent must infer when this tool is preferable to the repo-scoped siblings.

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