Skip to main content
Glama

bridge_uninstall

Removes bridge files from a Deadlock addon VPK while preserving other compiled overrides, cleaning up a bridge installation without deleting unrelated mod assets.

Instructions

Remove the bridge files from the addon VPK (other compiled overrides stay).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 exist, so the description carries the full behavioral burden. It does valuable work by disclosing exactly what is destroyed (bridge files) and what survives (other compiled overrides), which is the most important fact for a mutation tool; however, it says nothing about reversibility (bridge_install), required addon/mount state, or that the VPK itself is rewritten in place.

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 tight sentence with the action front-loaded and the scope qualifier appended where it is most useful. Every clause earns its place, with no redundant restatement of the tool name.

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 zero-parameter tool with an output schema, the description is nearly complete: the operation's target and its blast radius are stated. What is missing is prerequisite state and reversibility, which matter for an unannotated destructive operation on a VPK.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add and the 100% schema coverage leaves nothing undocumented. Baseline 4 applies for a parameterless tool.

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?

The description names a specific verb and resource ('Remove the bridge files from the addon VPK') and scopes it precisely with the parenthetical '(other compiled overrides stay)'. That parenthetical implicitly separates it from remove_override, though it never names bridge_install as the counterpart or any sibling explicitly.

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 only implied: an agent can infer it should be used when it wants the bridge files out of the VPK. There is no explicit when-to-use, no statement of prerequisites (e.g. whether the addon must be mounted first or the game closed), and no named alternative such as remove_override.

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