Skip to main content
Glama

compile_source

Compile a Panorama source file with CSDK 13 and pack it into the addon VPK as a permanent override (takes effect after a game restart).

Instructions

Compile a Panorama source file with CSDK 13 and pack it into the addon VPK as a permanent override (takes effect after a game restart).

path: e.g. 'panorama/layout/citadel_hud_top_bar.xml' or 'panorama/styles/hud.css'. To override a game file, start from ui_source(...) and keep the same path. The bridge host layouts (base_hud, base_dashboard, base_hud_and_db_overlay) can't be overridden: that would remove the bridge from that UI.

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>",
      "source": "<source>"
    },
    "name": "compile_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
sourceYes
installNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 persistence ('permanent override'), the delayed effect ('takes effect after a game restart'), and a hard restriction (bridge host layouts would remove the bridge). It omits what happens on repeated compiles or whether an existing override is replaced, and says nothing about the `install` flag behavior.

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?

The lead sentence front-loads purpose and outcome, followed by the path example and the override constraint. Nothing is wasted, though the parenthetical restart warning could be folded more tightly.

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 mutation tool with a significant side effect (permanent VPK override), the description covers the critical facts an agent needs before invoking it, and an output schema exists so return values need not be described. The unexplained `install` default is the main residual gap.

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%, so the description must compensate. It does for `path`, giving examples and the same-path constraint, but `source` and especially `install` (which apparently controls whether the result is installed) are left entirely to the schema's bare titles.

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 opens with a specific verb and resource ('Compile a Panorama source file'), names the toolchain (CSDK 13), and states the concrete outcome (packed into the addon VPK as a permanent override). This is clearly distinguishable from siblings like css_apply, xml_load, or layout_live_edit.

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?

It gives a clear workflow ('start from ui_source(...) and keep the same path') and an explicit exclusion (bridge host layouts cannot be overridden). It doesn't contrast against remove_override or list_overrides for managing existing overrides, but the positive usage path is unambiguous.

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