Skip to main content
Glama

build_compile_scripts

Compiles project game scripts in a separate headless Flax Editor process and returns structured compiler errors with file, line, code, and message.

Instructions

Compiles the game scripts in a separate headless Flax Editor process, with a time limit of 2 minutes. Returns structured compiler errors (file, line, code, message) from the engine log. The tool fails when a Flax Editor is open on the project. With the editor open, use build_check_scripts to find errors, or editor_compile to compile and reload.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorsYes
exitCodeYes
timedOutYes
succeededYes
errorCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.6/5.0
Behavior4/5

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

Goes beyond the lone readOnlyHint=false annotation by disclosing the 2-minute time limit, the failure mode when the editor is open, and the shape of returned compiler errors. Minor gap: it doesn't say whether the call blocks for the full duration or how to poll/follow up if it times out.

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 short sentences, each carrying distinct information: capability, time limit, return shape, failure condition and fallbacks. The most decision-relevant facts (headless, 2-min cap) are 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?

With an output schema present and no parameters, the description only needs to cover behavior and selection, which it largely does. Slight incompleteness around what happens if the 2-minute limit is hit (error vs. partial output) and whether the call is blocking.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description does not waste effort restating a nonexistent schema.

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 (compiles) and resource (game scripts) plus a distinctive mechanism (separate headless Flax Editor process, 2-minute limit). An agent can tell this apart from build_check_scripts and editor_compile without opening 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the blocking condition (a Flax Editor open on the project) and routes the agent to two named alternatives, build_check_scripts for error finding and editor_compile for compile-and-reload. This is exactly the when/when-not/alternatives pattern.

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