Skip to main content
Glama

Start uploading a custom modpack

startModpackUpload

Only for an assistant that can send the user's file with HTTP PUT, such as a coding agent with a shell. Begins uploading a Modrinth .mrpack or a CurseForge modpack .zip (up to 1 GiB). Returns uploadId, key, fileName and parts (url valid one hour): PUT each piece, keep each ETag, then completeModpackUpload. Installing is refused while a modpack is set unless completeModpackUpload is called with replace.

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

Input Schema

NameRequiredDescriptionDefault
bodyNo
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false, idempotent=false) the description discloses the concrete return payload (uploadId, key, fileName, parts), the one-hour validity of the part URLs, the ETag retention requirement, and a non-obvious side effect that blocks installs until completeModpackUpload is called with replace. That is real behavioral context an agent cannot infer from the hints.

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?

Content is front-loaded: capability precondition first, then what is uploaded, then the return and follow-up flow, then the replace constraint. The final clause about installing being refused is densely packed and reads as a run-on, but no sentence is filler.

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?

There is no output schema, and the description compensates by enumerating the returned fields and URL expiry, so the agent knows how to proceed to the PUT stage. For a multi-step, stateful upload starter with nested objects, the only omissions are the alternative recovery tools (abortModpackUpload, inspectModpackUpload), which is a minor gap.

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

Parameters4/5

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

The description adds meaning beyond the raw schema by constraining the accepted file types (.mrpack / CurseForge .zip) and restating the 1 GiB ceiling that the schema expresses only as a maximum of 1073741824. It explains the parts payload relationship that drives partCount, though it never mentions the serverId path parameter or that partCount is ceil(fileSize / 8388608), which the schema handles but the description leaves unremarked.

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?

"Begins uploading a Modrinth .mrpack or a CurseForge modpack .zip (up to 1 GiB)" names a specific verb, the exact accepted file formats, and a size bound, which cleanly separates it from siblings like startAssetUpload and startWorldUpload. An agent can identify the resource and the accepted inputs without opening the 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?

The first sentence is an explicit when-to-use gate: "Only for an assistant that can send the user's file with HTTP PUT, such as a coding agent with a shell," which tells the agent to skip this tool when it cannot perform raw PUTs. The rest of the description supplies the required follow-up sequence (PUT each piece, keep each ETag, then completeModpackUpload) and a when-not condition (installing is refused while a modpack is set unless replace is used).

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