Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Create file

gitea_create_file
Destructive

Create a new file in a Gitea repository and commit it with a message, with optional branch and author details.

Instructions

[UNIFIED] Create a new file in a Gitea repository with commit message.

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>",
      "path": "<path>",
      "content": "<content>",
      "message": "<message>"
    },
    "name": "gitea_create_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
repoYes
siteYes
ownerYes
branchNo
contentYes
messageYes
new_branchNo
author_nameNo
author_emailNo
content_is_base64No

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, destructiveHint=true and idempotentHint=false, so the description owes little on safety. It adds only 'with commit message' and says nothing about what happens when the path exists, whether a branch is auto-created, or how base64 content and author identity are handled.

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?

A single front-loaded sentence with no padding, which is structurally clean. The brevity here reflects under-specification rather than economy, and the '[UNIFIED]' token earns no place without explanation.

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 an 11-parameter destructive write with no output schema and zero schema descriptions, one sentence is far short. Critical concepts (branch targeting, creating a new branch, base64-encoded content, commit authorship) are entirely undocumented.

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 must compensate and does not. It never mentions branch, new_branch, author_name, author_email, or content_is_base64 — parameters an agent will otherwise pick values for blind.

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?

States a specific verb and resource ('Create a new file in a Gitea repository') and notes the commit message requirement, which distinguishes it from gitea_update_file and gitea_delete_file by implying a brand-new path. The '[UNIFIED]' prefix is unexplained noise but does not obscure the purpose.

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?

No guidance on when to use this versus gitea_update_file (existing file) or gitea_create_files (bulk), and no note that creation fails if the path already exists. The agent must infer the choice from names 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