Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Upload abort

gitea_upload_abort
Destructive

Aborts an active Gitea binary upload session and removes its associated spill file, stopping incomplete uploads and cleaning up temporary data.

Instructions

[UNIFIED] Abort a Gitea binary upload session and delete its spill file.

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_abort"
  }
}

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 already flag destructiveHint=true and idempotentHint=false, and the description adds meaningful context beyond that: it says the spill file is deleted, telling the agent that local/temporary data is destroyed and that aborting is not a resumable state. It does not clarify error behavior on an unknown or finished session, which is the remaining gap.

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?

A single front-loaded sentence with the destructive side effect attached, so nothing is buried. The bracketed "[UNIFIED]" tag adds no informational value and mildly clutters the opening.

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 simple two-parameter destructive operation with no output schema and annotations covering the safety profile, the description is close to sufficient. The missing piece is parameter-level guidance, especially what site and session_id must contain, which is not covered by any structured field.

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% for both parameters, so the description carries the full burden of explaining them, and it says nothing about what "site" identifies (a Gitea instance selector) or what "session_id" refers to or where it comes from. The agent must infer both from parameter names alone.

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 states a specific verb and resource ("Abort a Gitea binary upload session") plus the side effect of deleting the spill file, which clearly separates it from the sibling upload lifecycle tools (chunk, finish, status). 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 Guidelines3/5

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

Usage is implied by the name and the "abort" verb: call it to cancel an in-progress upload session. However, there is no explicit guidance on when to abort versus when to call gitea_upload_finish or gitea_upload_status, and no mention of behavior when the session has already completed or does not exist.

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