Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Create branch

gitea_create_branch

Create a new branch in a Gitea repository from an existing branch or commit to isolate development work and manage features separately.

Instructions

[UNIFIED] Create a new branch in a Gitea repository from existing branch or commit.

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>",
      "new_branch_name": "<new_branch_name>"
    },
    "name": "gitea_create_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYes
siteYes
ownerYes
old_ref_nameNo
new_branch_nameYes
old_branch_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already disclose that this is a non-read-only, non-idempotent, non-destructive operation. The description adds useful context that a branch can be created from either an existing branch or a commit, but it omits behavior such as what happens if the branch already exists, authentication requirements, or whether the operation fails when the base ref is invalid.

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?

The description is a single front-loaded sentence with little waste. The '[UNIFIED]' prefix is unexplained noise, but the sentence otherwise communicates the action efficiently.

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

Completeness2/5

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

For a creation tool with six parameters at 0% schema description coverage and no output schema, the description is too thin. It leaves the optional source parameters ambiguous and says nothing about failure conditions or the result of the operation.

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% for six parameters, so the description must compensate. It mentions the new branch and that the source can be a branch or commit, but it does not explain the distinction between old_branch_name and old_ref_name, the role of site/owner/repo, or the defaults and optionality of the two old_* parameters.

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 states a specific verb and resource: create a new branch in a Gitea repository. It also clarifies that the branch source may be an existing branch or commit, which is more informative than the title alone. It does not explicitly distinguish from siblings like delete_branch or get_branch, but the action is unambiguous.

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 use this tool versus alternatives, nor any prerequisites such as required permissions or repository state. Usage is merely implied by the create action.

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