Skip to main content
Glama

ui_files

Lists Panorama UI files shipped in Deadlock's game VPK and filters them by regex pattern, helping locate HUD and interface assets for inspection or modding.

Instructions

List Panorama files shipped in the game VPK (regex filter), e.g. pattern='hud'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ui_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
patternNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 discloses a useful scope constraint (only files shipped in the VPK, i.e. not loose/modified files) and implies a read-only listing, but says nothing about whether the 300-item default truncates results or whether large listings need paging.

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 front-loaded sentence with the resource and scope first, then the filter format, then an inline example. No filler words.

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?

Output schema exists, so return shape need not be described, and this is a simple two-parameter listing tool. The one real gap is the undocumented 'limit' behavior (truncation vs pagination), which matters for a tool that can return hundreds of files.

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 coverage is 0%, so the description must compensate. It successfully clarifies that 'pattern' is a regex (not a substring or glob) and gives a concrete example, which the schema does not. 'limit' remains entirely unexplained, costing it a point.

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?

Specific verb plus resource: 'List Panorama files shipped in the game VPK', with a stated filtering capability (regex). The VPK scope qualifier distinguishes it meaningfully from tools like ui_source, though no sibling is named explicitly and the title is null.

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 example 'e.g. pattern='hud'' implicitly shows the discovery/browse use case, but there is no explicit statement of when to choose this over ui_source, panel_find, or panel_tree, and no when-not guidance.

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