Skip to main content
Glama

bridge_install

Build and install the in-game bridges (needs CSDK 13 + Source2Viewer-CLI): one per UI root (HUD, dashboard, overlay). Compiles each host layout override + bridge script into the addon VPK.

Instructions

Build and install the in-game bridges (needs CSDK 13 + Source2Viewer-CLI): one per UI root (HUD, dashboard, overlay). Compiles each host layout override + bridge script into the addon VPK. launch_game mounts the addon for its session (mount=True mounts it now). Restart the game afterwards. Re-run it after a game update or an update of this tool (status says when).

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_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
mountNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses external tool/version dependencies, that artifacts are written into the addon VPK, that a game restart is needed for changes to take effect, and that re-running is expected and safe after updates. It doesn't say what happens to existing bridges/VPK contents or how failures surface, which keeps it below a 5 for a mutating tool.

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 action and prerequisites are front-loaded, and each following sentence adds new information (granularity, compile target, mount option, restart, re-run policy) rather than restating. The nested parentheticals make it dense and slightly harder to scan than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a dependency-heavy build/install tool with an output schema already covering results and only one optional boolean parameter, the description supplies everything an agent needs to decide to call it and what to do afterwards (restart, re-run when status indicates). Remaining unknowns, such as overwrite semantics for existing bridges, are minor relative to this coverage.

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% for the single 'mount' parameter, so the description must compensate, and it does: 'launch_game mounts the addon for its session (mount=True mounts it now)' explains both the default behavior and what the flag changes. The only gap is that it doesn't state the mount's lifetime or persistence beyond 'now'.

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?

States a specific compound verb and resource ('Build and install the in-game bridges') plus the granularity ('one per UI root (HUD, dashboard, overlay)') and the mechanism ('Compiles each host layout override + bridge script into the addon VPK'). This clearly separates it from siblings like bridge_uninstall, compile_source, and launch_game without needing to open any schema.

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?

Gives concrete when-to-run context: prerequisites (CSDK 13 + Source2Viewer-CLI), a post-run requirement ('Restart the game afterwards'), and re-run triggers ('after a game update or an update of this tool (status says when)'), and it points at launch_game for mounting. It stops short of naming when to prefer it over compile_source or when bridge_uninstall is the right call, so it's clear context without explicit exclusions.

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