Skip to main content
Glama

List the files in the server's uploaded modpack

getModpackMembers
Read-onlyIdempotent

Reads the uploaded modpack's manifest and the jars it bundles. The first request starts reading in the background and answers status parsing; ask again until status is ready.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavior: the call is asynchronous, the first invocation only kicks off background work, and repeated polling is required until ready — information an agent cannot get from the 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?

Two tight sentences with no filler, and the core action is front-loaded before the polling caveat. Slightly terse on what the returned status values are, but nothing is wasted.

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?

Covers the async polling contract, which is the main complexity here, and there is no output schema to explain. However, it never enumerates the possible status values or describes what the ready payload contains (manifest entries, jar list), leaving the agent to guess when polling should stop.

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% and the single parameter is a nested object requiring serverId. The description never mentions the path/serverId argument or its format, so it adds no meaning beyond the schema, which itself only lightly documents serverId as coming from listServers.

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?

States a specific verb and resource: reads the uploaded modpack's manifest and the jars it bundles. That is concrete enough to distinguish it from upload-lifecycle siblings like startModpackUpload or abortModpackUpload, though it does not explicitly contrast with inspectModpackUpload.

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?

Gives clear operational guidance for the async pattern: the first call starts background parsing and returns a parsing status, and the caller should re-ask until status is ready. It does not say when to prefer this over inspectModpackUpload or other modpack tools, so usage context is implied rather than stated.

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