Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Upload finish

gitea_upload_finish
Destructive

Finalizes a Gitea binary upload session by verifying an optional SHA-256 checksum and sending the original bytes to Gitea as multipart/form-data for release assets.

Instructions

[UNIFIED] Finalize a complete Gitea binary upload session. For release_asset sessions this verifies optional sha256, then sends the original bytes to Gitea as multipart/form-data.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare destructive/not-idempotent; the description adds genuine context by disclosing that sha256 verification occurs for release_asset sessions and that the original bytes are transmitted as multipart/form-data at finish time (i.e., the actual send happens here, not during chunking). It stops short of saying what happens to the session on failure or whether a failed finish can be retried.

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 dense sentences with the core action front-loaded and no filler. The bracketed "[UNIFIED]" token is marginal noise but costs little.

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 two-parameter finalize tool with no output schema, the description covers the action and one internal behavior but omits how the session is obtained (start/chunk flow), what the caller receives back, and the failure/retry semantics of a non-idempotent destructive operation. Adequate but with clear gaps.

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 coverage is 0% and the description never explains either parameter: it does not say that session_id is the handle returned by gitea_upload_start, nor what site selects. It also references a sha256 verification concept that has no corresponding schema field, so an agent cannot map the described behavior to inputs.

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: "Finalize a complete Gitea binary upload session," and scopes the notable branch ("For release_asset sessions"). This clearly separates it from gitea_upload_start/chunk/abort/status by naming the finalization step, though it does not name those siblings 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?

The phrase "complete ... upload session" implies this is the last step after chunking, and the "[UNIFIED]" prefix hints it covers more than one session type, but the description never states prerequisites or when to call status/abort instead. Usage is inferable but not spelled out.

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