Skip to main content
Glama

export_mod

Export compiled overrides as a standalone mod VPK (no bridge files) at /mods//pak01_dir.vpk.

Instructions

Export compiled overrides as a standalone mod VPK (no bridge files) at /mods//pak01_dir.vpk.

include: regex selecting which addon files to export (default: every non-bridge override; see list_overrides). install=True also copies it into game/citadel/addons/ as the next free pakNN_dir.vpk (re-installing the same name replaces its earlier copy); the game loads it on its next start.

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": {
      "name": "<name>"
    },
    "name": "export_mod"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
includeNo
installNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / install
      Added value: +{
      +  "default": false,
      +  "title": "Install",
      +  "type": "boolean"
      +}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the write target path, that bridge files are excluded, that re-installing the same name replaces the prior copy, and that the game only picks it up on next start. It doesn't mention overwrite behavior for the non-install export path if a VPK already exists.

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?

Front-loads the core action and output path, then details include and install semantics in a compact block. Parenthetical asides are informative rather than filler; slightly dense but no wasted sentences.

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?

An output schema exists, so return values needn't be explained; the description instead covers destination, filtering defaults, and install side effects. What remains thin is failure/precondition behavior (e.g., what happens with no compiled overrides or an invalid regex), which is modest for a tool of this complexity.

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?

Schema description coverage is 0%, so the description must compensate, and it explains all three: name appears in the output path and install filename, include is a regex with a documented default ('every non-bridge override'), and install is a boolean with its side effect spelled out. The regex syntax/format of include is not illustrated, a minor 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?

States a specific verb and artifact ('Export compiled overrides as a standalone mod VPK'), scopes it ('no bridge files'), and gives the exact output path pattern, so the agent knows precisely what this produces and how it differs from sibling addon/bridge operations.

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?

Clearly frames the two modes: default export to <data dir>/mods/<name>/pak01_dir.vpk versus install=True copying into game/citadel/addons/. It points to list_overrides for choosing which files to include. It does not explicitly say when to prefer this over addons_mount or bridge_install, leaving that inference to the agent.

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