Skip to main content
Glama

run_bsp_rename

Renames a compiled .bsp and the content packed inside it, such as nodegraph and soundscripts, so the engine still finds them by the new map name. Writes a new file, leaving the original intact.

Instructions

Renames a compiled .bsp AND the content packed inside it -- the nodegraph, cubemap patches, soundscripts, anything under maps//. Renaming the file alone orphans every one of them: the engine looks them up by the map's name, finds nothing, and says nothing, so the symptom is Nextbots that will not path or a missing soundscape rather than an error. Drives ficool2's bsp_rename, which is a separate download; health says whether it is installed. Writes a NEW .bsp beside the old one and leaves the original alone.

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": {
      "bsp": "<bsp>",
      "newName": "<newName>"
    },
    "name": "run_bsp_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
bspYesPath to the .bsp, absolute or relative to the repo root.
confirmNoRequired (true) to run this tool: it writes or executes.
newNameYesThe new map name, without the .bsp suffix. Letters, digits, _ - . only.

Output Schema

NameRequiredDescriptionDefault
okYes
bspYes
noteYes
toolYes
newNameYes
renamedYes
writtenYes
exitCodeYes
timedOutYes
bytesAfterYes
stdoutTailYes
bytesBeforeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A3.9/5.0
Behavior3/5

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

Annotations carry only a title, so the description must supply behavioral detail, and it does well: external dependency (ficool2's bsp_rename is a separate download, verify via health) and a clearly stated side effect (writes a NEW .bsp beside the original, leaving the original untouched). It omits failure/error behavior when the tool is missing and any confirmation mechanics, despite confirm being a required-to-set parameter.

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?

Four sentences with no filler: the core action first, then why the naive approach fails (including the silent-failure symptom that makes the warning credible), then the dependency, then the output behavior. The symptom detail about Nextbots not pathing and missing soundscapes earns its length by making the consequence concrete.

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

Completeness3/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 no explanation, and the description covers dependency, side effects, and failure symptoms. The remaining gap is moderate: behavior when bsp_rename is absent, and the fact that confirm must be set true to actually run, are left to the schema rather than integrated into the narrative.

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 100%, so bsp, newName, and confirm are already fully documented in the schema, including the name character restrictions. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 verb (renames) and two specific resources (the .bsp file and its packed contents), and enumerates the kinds of packed content affected (nodegraph, cubemap patches, soundscripts, maps/<name>/). This is clearly distinguishable from read-only siblings like read_bsp_info or read_bsp_entities.

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?

Explains the motivating condition for using it -- renaming the file alone silently orphans packed content -- and points at health to check whether the external bsp_rename tool is installed, which is a real prerequisite. It does not explicitly name a sibling alternative or state when not to use it, keeping it below a 5.

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