Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Create pull request

gitea_create_pull_request

Create a new pull request in a Gitea repository by specifying the site, owner, repository, title, source branch, and target branch.

Instructions

[UNIFIED] Create a new pull request in a Gitea repository.

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>",
      "title": "<title>",
      "head": "<head>",
      "base": "<base>"
    },
    "name": "gitea_create_pull_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYes
bodyNo
headYes
repoYes
siteYes
ownerYes
titleYes
labelsNo
assigneeNo
assigneesNo
milestoneNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the description is not the sole carrier of the safety profile. Beyond that, the description says nothing about failure modes, whether duplicate PRs error, whether the optional labels/assignee/milestone values must pre-exist, or what a caller gets back.

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?

One short sentence, front-loaded with the verb and resource, so nothing is wasted in a literal sense. However the brevity stems from under-specification rather than disciplined editing, and the bracketed "[UNIFIED]" tag occupies prime space without meaning.

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 write tool with 11 parameters, 6 of them required and no output schema, the description is far too thin. An agent cannot confidently construct the head/base arguments or populate the optional metadata fields from this definition alone.

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

Parameters1/5

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

Schema description coverage is 0% across 11 parameters, so the description carries the full explanatory burden and delivers none of it. Critical semantics are entirely absent: head vs base branch direction, what format owner/repo/site take, and whether labels/assignees/milestone accept names or IDs.

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?

"Create a new pull request in a Gitea repository" gives a specific verb (create) and resource (pull request) with the owning system named, which distinguishes it from siblings like gitea_create_issue or gitea_create_branch. The unexplained "[UNIFIED]" prefix adds no information and the description does not state how this differs from gitea_update_pull_request or gitea_create_pr_review.

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 versus alternatives, and no prerequisites are stated (e.g., that the head branch must already exist, or that gitea_create_branch should be called first). The agent must infer the entire workflow from the tool name alone.

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