Skip to main content
Glama

Start uploading a custom mod or plugin file

startAssetUpload

Only for an assistant that can send the user's file with HTTP PUT, such as a coding agent with a shell. Begins uploading one .jar or .zip mod, plugin, datapack or resource pack (up to 512 MiB, storage capped per server and account) and returns uploadId, key, fileName and parts: PUT each piece within an hour and keep each ETag. Then completeAssetUploads installs mods, plugins and datapacks, inspectAssetUpload checks a file or readies a resource pack for setResourcePack, and abortAssetUploads discards it.

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": {
      "path": "<path>"
    },
    "name": "startAssetUpload"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / body / properties / replace
      Added value: +{
      +  "description": "Replace the uploaded file that already has this name. Its entry keeps its place and disabled state and takes the new file once the upload completes.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only give the generic safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false); the description adds substantial context beyond that: the 512 MiB per-file ceiling, account/server storage caps, the fact that it returns uploadId, key, fileName and parts, and the operational contract that each part must be PUT within an hour with its ETag retained. That multipart protocol detail is exactly the kind of behavior an agent cannot infer from annotations.

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?

The gating prerequisite and the action come first, followed by limits, return values, and sibling routing — a logical front-loaded order with no filler. It is a single dense paragraph with long compound sentences, which costs a little scannability but no sentence is wasted.

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

Completeness5/5

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

Even without an output schema, the description enumerates the returned fields (uploadId, key, fileName, parts) and the follow-up obligations, and it covers size limits and the full downstream tool chain. For a two-parameter multipart upload starter with nested objects, nothing an agent needs to call it correctly is missing.

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

Parameters3/5

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

Reported schema coverage is 0%, so by default the description must carry parameter meaning; it names fileName and the notion of 'parts' and gives the size ceiling, but it never explains the nested `replace` semantics, the partCount formula, or the serverId path argument. The input schema itself does document those nested fields, which keeps this at a minimum-viable 3 rather than lower.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb and resource ('Begins uploading one .jar or .zip mod, plugin, datapack or resource pack') and names the exact artifact types it accepts. It also distinguishes itself from the sibling tools that handle the other phases (completeAssetUploads, inspectAssetUpload, abortAssetUploads), so an agent can place it in the upload lifecycle without opening another schema.

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

Usage Guidelines5/5

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

States a hard prerequisite up front ('Only for an assistant that can send the user's file with HTTP PUT, such as a coding agent with a shell'), which effectively tells the agent when NOT to use it. It then routes explicitly: completeAssetUploads to install, inspectAssetUpload to check, setResourcePack to ready a resource pack, abortAssetUploads to discard — each alternative tied to its condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources