Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Create repository

gitea_create_repository

Create a new Gitea repository for a user or organization, with optional auto-initialization, README, license, gitignore, and branch settings.

Instructions

[UNIFIED] Create a new Gitea repository. Can create user or organization repository with optional auto-initialization.

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

Input Schema

NameRequiredDescriptionDefault
orgNo
nameYes
siteYes
readmeNo
licenseNo
privateNo
auto_initNo
gitignoresNo
descriptionNo
default_branchNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive operation, so the safety profile is covered. The description adds that the target can be a user or org and that initialization is optional, but it omits failure behavior (duplicate names), permission requirements, and what auto-initialization actually creates.

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?

Two compact sentences with the core action front-loaded and no filler. The second sentence is slightly under-specified rather than wasteful, so it stays efficient.

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?

With 10 parameters, no schema descriptions, no output schema, and only basic annotations, the definition should explain the required 'site' parameter and the behavior of private/description/default_branch/auto_init. None of that is present, so an agent cannot call this correctly without inspecting the raw schema.

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

Parameters5/5

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

Schema coverage is 0% across 10 parameters, so the description carries the full burden. It identifies the org-vs-user targeting and the auto-initialization family of options (readme, license, gitignores), which is the only parameter-level meaning available; a 0% covered schema with no param info beyond this keeps it at 5.

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 uses a specific verb and resource ('Create a new Gitea repository') and adds the meaningful scope variation of user vs organization repository. It clearly separates itself from siblings like gitea_update_repository or gitea_delete_repository, though it does not name them explicitly.

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?

Usage is implied: call this when a new repository must be created, and the mention of user vs organization gives some selection context. There is no when-not guidance, no mention of what happens on a name collision, and no prerequisite information such as required auth or what 'site' refers to.

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