Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Set up Surge CI

surge_setup
Idempotent

Set up Surge CI on a repository by serving it and opening a pull request that points workflow jobs at Surge runners and adds the merge queue batch trigger.

Instructions

Set up Surge CI on one repository of the user's account: if Surge does not serve it yet, serve it (it joins the repositories Surge serves and gets the account's Surge settings), then open a pull request that points its workflow jobs at Surge runners and adds the merge queue batch trigger. Nothing in the repository's files changes until that pull request is merged. The answer says what happened, with the pull request link.

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

Input Schema

NameRequiredDescriptionDefault
repoYes
ownerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare non-read-only, idempotent, non-destructive and open-world, but the description adds genuinely new context: the account-level side effect of serving the repo with the account's Surge settings, and the reassurance that no repository files change until the PR is merged. It also states the response includes a PR link, which the annotations cannot convey. It stops short of auth/permission requirements or what happens on failure or when a PR already exists.

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?

A single front-loaded sentence with the effect chain in order (serve → configure → open PR), followed by the non-destructive guarantee and the return value. Dense and purposeful, though the nested clauses make it one long read.

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 an open-world mutation that touches account state and opens a PR, the description covers what changes, what does not change yet, and what the response contains. Remaining gaps — identifier formats, permission prerequisites, and error behavior — are relatively minor given idempotentHint and no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry both parameters, and it does so only indirectly — 'one repository of the user's account' hints that repo identifies the target, but owner is never explained (user vs org) and no name/format expectations are given. An agent must guess the identifier format for a destructive-in-scope, outward-facing setup call.

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 ('Set up Surge CI on one repository') and spells out the exact sequence it performs: enroll the repo in Surge, then open a PR rewiring workflow jobs to Surge runners and adding the merge-queue batch trigger. An agent can tell this apart from settings tools like settings_set or repo_settings_set, which do not create pull requests or enroll repositories.

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 phrase 'on one repository of the user's account' implies a single-repo, per-call scope, which is useful usage context. But there is no explicit when-to-use vs when-not guidance, no prerequisites (permissions, repo state), and no pointer to related tools for configuring settings afterward.

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