Skip to main content
Glama

rebuild

Repacks archives, APKs, and Unreal PAK files; validates table offsets and templates; and dispatches module/action tasks for game-modding workflows.

Instructions

Rebuild/repack helpers. Dispatches by module+action.

Modules/actions: tables: rebuild_offsets (path, schema), validate (path, schema) archives: repack (src_dir, out_path, format) apk: apk_repack unreal: unreal_pak pack format: validate_template

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": {
      "module": "<module>",
      "action": "<action>"
    },
    "name": "rebuild"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
moduleYes
paramsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does make clear this is a mutating rebuild/repack dispatcher (repack writes to out_path), which is meaningful, but it never states overwrite behavior, required permissions, reversibility, or failure handling. With an output schema present, return-value explanation is not required, but the mutation-safety gap remains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A one-line purpose followed by a compact, front-loaded dispatch table with no filler. Every line carries information an agent needs to select a module/action pair.

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?

For a six-branch dispatcher with zero schema coverage and no annotations, the dispatch table is the single most important piece of documentation and it is present. What is missing is per-action semantics and valid argument values, so the definition is adequate but leaves real ambiguity before invocation.

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?

Schema description coverage is 0% for all three parameters, so the description has to compensate; it usefully maps parameter names per action (path/schema, src_dir/out_path/format), which is real added meaning. However it never explains what those values mean, what valid `format` values are, or how the `params` object should be keyed, leaving the core dispatch parameter underspecified.

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?

The description states the tool is a dispatcher moving on module+action and then enumerates the concrete module/action pairs (tables, archives, apk, unreal, format) with their argument names, so an agent can see the resources involved. It is not fully clear what each action actually does (e.g. rebuild_offsets vs repack), which keeps it below a 5, and the internal 'tables: validate' action overlaps with the sibling tool named 'validate' without any differentiation.

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?

The module list implies when each branch applies, but there is no explicit guidance on when to choose this tool over siblings such as validate, patch_code, or export, nor which module fits which situation. Usage is inferable only by domain knowledge of the module names.

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