Skip to main content
Glama

Finish a modpack upload and install it

completeModpackUpload
DestructiveIdempotent

Installs the uploaded file as the server's modpack, replacing loader, version and mods at the next restart; a backup is taken first. Pass uploadId, key and each ETag, and replace to swap out a modpack that is already set. Returns the server.

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

Input Schema

NameRequiredDescriptionDefault
bodyNo
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / body / properties / curseforgeProjectId
      Added value: +{
      +  "description": "CurseForge project the .zip was downloaded from, to show its logo.",
      +  "maxLength": 20,
      +  "pattern": "^\\d+$",
      +  "type": "string"
      +}
    • addedInput schema / properties / body / properties / replace
      Added value: +{
      +  "description": "Swap out the server's current modpack in the same step.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.1/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 description's extra value is timing and mitigation: changes take effect at the next restart and a backup is taken first. That is meaningful disclosure an agent would not get from annotations alone. It leaves out failure behavior (e.g. what happens if parts are missing) and any permission requirements.

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 sentences, front-loaded with the effect and timing of the operation, then the call-specific inputs and return value. The parameter recital in the second sentence is somewhat redundant with the schema but remains compact and readable.

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 destructive, nested-parameter tool with no output schema, the description covers what changes, when it applies, the backup safety net, and the return value ('Returns the server'). Only the multipart-prerequisite chain and error conditions are left unstated, which an agent could infer from the schema's key/uploadId fields.

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?

The description names uploadId, key, each ETag and replace, matching the required body fields, but adds no meaning beyond the schema's own nested descriptions (which already explain ordering and that the ETag header quotes are included). It says nothing about curseforgeProjectId or path.serverId, so with a reported 0% schema description coverage it does not fully compensate for the gap.

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?

The description gives a specific verb and resource — installs the uploaded file as the server's modpack — plus scoping detail (loader, version and mods, applied at next restart). It is clearly distinguishable from siblings such as startModpackUpload, inspectModpackUpload, abortModpackUpload and completeWorldUpload, which share a prefix but do different things.

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?

Context is clear: this is the terminal step for a multipart modpack upload, and the description states the conditional case for 'replace' (swapping out a modpack that is already set). It does not explicitly name prerequisites (all parts uploaded first) or point to abortModpackUpload as the alternative when the upload should be abandoned, so it stops short of a 5.

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