Skip to main content
Glama

addons_mount

Add or remove the dev addon search path in gameinfo.gi so the game mounts it during launch and unmounts it on exit, while removal keeps the standard mod folder mounted.

Instructions

Add (or remove) the dev addon search path in gameinfo.gi. launch_game mounts it and unmounts it when the game exits; removing it keeps the standard mod folder mounted.

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

Input Schema

NameRequiredDescriptionDefault
enableNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/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 and does substantial work: it discloses the mutation target (gameinfo.gi), the interaction with launch_game's automatic mount/unmount on exit, and the effect of removal (standard mod folder stays mounted). It omits error behavior, whether the original file is backed up, and whether changes require the game to be closed.

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 dense sentences with no filler, and the core action is front-loaded. The second sentence is slightly run-on and 'removing it' is a touch ambiguous about whether 'it' is the addon or the search path, but no content is wasted.

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?

An output schema exists, so return values need not be explained, and the description adequately covers the config-file mutation and its lifecycle relationship with launch_game. For a mutation tool with no annotations, more on failure modes and required game state would round it out.

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?

There is one boolean parameter (enable, default true) with 0% schema description coverage. The description's 'Add (or remove)' implies the toggle semantically, but it never explicitly states that the parameter selects add vs. remove, nor mentions the default. Partial compensation for the coverage gap.

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?

The description names a concrete verb pair (add/remove), the exact resource (the dev addon search path in gameinfo.gi), and implicitly clarifies that 'mount' means editing a config file rather than a runtime operation. An agent can distinguish it from launch_game, which performs the actual mounting.

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?

It explains the selection logic fairly well: launch_game mounts the path automatically and unmounts on exit, so this tool is for persisting the path across sessions, and disabling it restores the standard mod folder. The when-to-use is clear by implication, but there is no explicit 'use this when you want X' statement or mention of prerequisites such as a stopped game.

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