Skip to main content
Glama

Finish uploads and install the files

completeAssetUploads
DestructiveIdempotent

Installs one or more (up to 50) files from startAssetUpload calls; resource packs go through setResourcePack. An upload with the same file name as an installed mod, plugin or datapack replaces that file. Files failing a check are returned in rejected with key and error; the rest apply at the next restart.

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": "completeAssetUploads"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered; the description goes beyond that by disclosing that same-named files are overwritten, that failures are partial (returned in 'rejected' with key and error), and that changes apply only at the next restart. That deferred-application detail is genuinely non-obvious. It omits permission requirements and what happens to rejected uploads (whether they must be aborted or 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?

Three front-loaded sentences with high information density and no filler; the 50-file limit and sibling routing come first. The heavy semicolon chaining makes it slightly compact to parse, but nothing is wasted.

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

Completeness4/5

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

For a nested 2-parameter mutation tool with no output schema, it covers the essential flow (start → complete), limits, overwrite semantics, partial-failure reporting, and next-restart application. It leaves out the shape of the success response and any auth or permission prerequisites, which would matter for a destructive operation.

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 reported as 0%, so the description should carry meaning about the inputs, but it adds almost none: it does not explain the uploads array, key/uploadId pairing, partNumber ordering, or the serverId path parameter. The only overlap ('up to 50') merely restates the schema's maxItems constraint.

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?

States a specific verb and resource ('Installs one or more (up to 50) files') and anchors the call to the sibling that precedes it ('from startAssetUpload calls'). It also routes a special case ('resource packs go through setResourcePack'), so an agent can tell this apart from sibling completion/abort tools.

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?

The description makes clear when to call it: after startAssetUpload, once parts are uploaded. It does not state when NOT to call it (e.g. call abortAssetUploads instead when a file fails, or use completeModpackUpload/completeWorldUpload for those asset types), so the exclusion guidance is implicit rather than explicit.

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