Skip to main content
Glama

ui_source

Decompiles a shipped Panorama UI file into readable source from paths like layout/base_hud or styles/hud.css, enabling inspection and modification of Deadlock interface assets.

Instructions

Decompile a shipped Panorama file to source, e.g. 'layout/base_hud' or 'styles/hud.css'.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
refreshNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and it is thin. It does not say whether decompiling writes files to disk or just returns text, whether results are cached, or what side effects (if any) occur. The existence of a 'refresh' parameter strongly suggests caching behavior that the description never explains.

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 single dense sentence with the verb and resource front-loaded, followed by immediately actionable path examples. No filler or redundancy.

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?

An output schema exists, so return values need not be explained. But for a no-annotation tool whose 'refresh' flag implies caching or forced regeneration, the description leaves key behavioral questions unanswered, making it only minimally sufficient.

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 add real meaning for 'path' by showing two accepted path shapes (a layout path and a CSS path), but 'refresh' is entirely unaddressed in both schema and description, leaving half the parameters opaque.

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 ('Decompile') and a specific resource ('shipped Panorama file'), and gives concrete path examples ('layout/base_hud', 'styles/hud.css'). It does not explicitly contrast with compile_source (the inverse) or ui_files (which presumably enumerates paths), so sibling differentiation is left to inference.

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 word 'shipped' implies this targets built-in game files rather than author overrides, which is a useful implicit signal. However, there is no explicit when-to-use statement, no mention of when to prefer ui_files or compile_source, and no prerequisites described.

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