Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Merge pull request

gitea_merge_pull_request
Destructive

Merge a Gitea pull request using a specified merge method, with optional title, message, and branch deletion for completing code changes.

Instructions

[UNIFIED] Merge a pull request using specified merge method.

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

Input Schema

NameRequiredDescriptionDefault
repoYes
siteYes
ownerYes
titleNo
methodNomerge
messageNo
pr_numberYes
delete_branch_after_mergeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not explain what happens to the source branch, whether merge conflicts are surfaced, or that a repeat call will fail rather than no-op. For a destructive mutation the description should carry more than a restatement of the name.

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 single sentence is tight and front-loaded with the action, but it is under-specified rather than concise, and the "[UNIFIED]" tag is noise that consumes attention without adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A destructive, non-idempotent, 8-parameter tool with zero schema description coverage and no output schema gets only one sentence. The agent is left guessing at merge method semantics, branch deletion behavior, and failure modes, which is inadequate for this complexity.

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% across 8 parameters, so the description must compensate and does not. Only the "method" parameter is hinted at, with no mention of the accepted values (merge/rebase/squash), and title, message, delete_branch_after_merge, and the site/owner/repo/pr_number addressing are entirely unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Merge a pull request"), which cleanly separates it from siblings such as gitea_close_pull_request or gitea_update_pull_request. It does not state scope preconditions or explicitly distinguish from other merge-adjacent operations, and the "[UNIFIED]" prefix carries no meaning for an agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to merge versus when to close or update a PR, and no prerequisites such as the PR being open or mergeable. It also omits the crucial warning that this action is irreversible once performed.

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