Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Merge Git Branch

mergeGitBranch
Destructive

Merges a named Git branch into the current branch as a merge commit unless it fast-forwards, aborting on failure and returning Git's error; works only on development apps.

Instructions

Merge the named branch into the current one, as a merge commit unless it fast-forwards. Refused while another merge, rebase, revert or cherry-pick is in progress. If the merge fails, it is aborted, the call fails, and the error carries git's report. Works only on a development app: any other app answers 403 read_only. Runs git in the app's running container and returns its output.

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": {
      "workspaceSlug": "<workspaceSlug>",
      "appSlug": "<appSlug>"
    },
    "name": "mergeGitBranch"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
regionNo
appSlugYes
requestBodyNoThe JSON request body.
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: fast-forward versus merge commit semantics, abort-on-failure behavior, error propagation with git's report, 403 read_only on non-development apps, and execution inside the app's running container. These details materially help an agent predict effects of this destructive mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense sentences, front-loaded with the primary action and followed by constraints and failure behavior. Every sentence adds useful operational meaning without repetition.

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 complex mutation with annotations covering destructiveness and open-world behavior and no output schema, the description explains return behavior and failure handling well. The main remaining gap is parameter-level detail for the five inputs.

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 only 20%, so the description needs to compensate, but it only clarifies the branch to merge and indirectly the development-only env requirement. It leaves workspaceSlug, appSlug, region, and the nested request body largely undocumented.

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: merge the named branch into the current branch, as a merge commit unless it fast-forwards. This clearly distinguishes it from sibling operations such as rebaseGitBranch, cherryPickGitCommit, and pullGitChanges.

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 explicit when-not conditions: refused while another merge, rebase, revert, or cherry-pick is in progress, and only usable on a development app. It does not explicitly route the agent to alternative sibling tools, but the operational constraints are clear.

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

Deploy Server

Other Tools