Skip to main content
Glama

remove_override

Removes a compile_source override from an addon VPK by path, restoring default game files after a restart.

Instructions

Remove a compile_source override from the addon VPK (e.g. 'panorama/styles/hud.css'). Takes effect after a game restart.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

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?

With no annotations, the description carries the full burden, and it does disclose one meaningful trait: the change only applies after a game restart. It omits other relevant behavior such as whether the override must already exist, error behavior on a bad path, or whether removal persists across exports.

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?

Two tight sentences: action plus example first, the restart caveat second. No wasted wording, and the most important fact (what gets removed) is front-loaded.

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?

A one-parameter tool with an output schema, so return shape needn't be explained; the description covers what is removed, the path format, and the timing side effect. Only edge cases (missing override, invalid path) remain unaddressed.

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% — the schema only says 'path' is a string. The description partially compensates by giving a concrete example ('panorama/styles/hud.css'), revealing the expected VPK-relative format, but does not state whether the path must match an existing override exactly or whether prefixes/globs are accepted.

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 and resource ('Remove a compile_source override from the addon VPK') and clarifies the target artifact, which separates it from siblings like compile_source and addons_mount. It does not explicitly name the related listing tool, but the action is unambiguous.

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?

Usage is implied by the verb and the example path, but there is no explicit guidance on when to use this versus list_overrides (to discover valid paths) or css_clear (to revert styling more broadly). An agent must infer that flow.

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