Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Upload start

gitea_upload_start
Destructive

Start a Gitea release asset upload session and get a per-user endpoint for sending raw file bytes with a Bearer token, with a 1-hour TTL and a 500 MB default cap.

Instructions

[UNIFIED] Start a Gitea binary upload session. First supported kind is release_asset. On per-user MCP endpoints this returns /u/{user_id}/{alias}/gitea-upload/{session_id}, so callers can PUT raw bytes with curl --data-binary @file using the same Bearer token. TTL 1h, hard cap 500 MB by default.

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>",
      "release_id": "<release_id>",
      "filename": "<filename>",
      "total_bytes": "<total_bytes>"
    },
    "name": "gitea_upload_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNorelease_asset
repoYes
siteYes
ownerYes
sha256No
filenameYes
release_idYes
total_bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare destructiveHint=true and non-idempotent; the description adds real behavioral facts the agent could not otherwise know: a 1-hour TTL, a 500 MB default hard cap, the shape of the returned upload path on per-user endpoints, and that the same Bearer token authorizes the PUT. It does not say what happens to a session that expires or is never finished.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the action, then the return-path/auth detail, then limits. Nothing is redundant and the limits land last where they are easiest to check.

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

Completeness3/5

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

For a destructive, multi-step upload with no output schema and 8 undocumented parameters, the description covers lifecycle (TTL, size cap, upload URL, auth) well but leaves the identity/scope parameters and the sha256 integrity option undefined. Enough to start correctly, not enough to use every parameter confidently.

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 carries the full burden, yet it only implicitly touches kind (release_asset) and total_bytes (500 MB cap). site, owner, repo, release_id, filename, and especially sha256 — which presumably enables integrity verification — are never explained.

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 — 'Start a Gitea binary upload session' — and scopes it with 'First supported kind is release_asset'. The start/chunk/finish/abort workflow is inferable from the naming, but no sibling is named explicitly to confirm the boundary.

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

Usage Guidelines4/5

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

Gives clear operational context: callers PUT raw bytes to the returned URL with curl --data-binary and the same Bearer token. It does not state exclusions, e.g. when to use gitea_upload_release_asset directly instead for small assets, so it stops short of full when/when-not guidance.

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