Skip to main content
Glama

build_check_scripts

Read-only

Compiles project script modules outside the editor using the last Flax.Build arguments and current files, returning structured compile errors and warnings without changing the project.

Instructions

Compiles the project's script modules, and those of the projects it references, outside the editor into a scratch folder. It uses the compiler arguments that Flax.Build last used and the current files of the modules. Returns passed, failed or unavailable (never built: Reason tells why), with structured errors and warnings (file, line, column, code) and the outcome of each module. It works while the editor is open, also during play mode. It changes nothing in the project. Use it to find compile errors fast. It does not load the change into the editor: for that, use editor_compile.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorsYes
reasonYes
statusYes
modulesYes
secondsYes
warningsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond readOnlyHint=true: it states no project changes are made, that it reuses the compiler arguments Flax.Build last used with current module files, and it works during editor play mode. It also discloses the tri-state outcome (passed/failed/unavailable) and that the unavailable reason is carried in a Reason field.

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?

Front-loaded with the core action, then constraints, then outcome, then routing to the sibling — a good ordering. It is slightly long, and the enumerated return-value detail (file, line, column, code, per-module outcome) overlaps the existing output schema.

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 zero-parameter tool with an output schema, the description supplies everything an agent needs: what it does, that it is safe/non-mutating, when it works, and which sibling to use for the other intent. Nothing decision-relevant is missing.

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 nothing to disambiguate and the baseline is 4. The description correctly spends no words on parameter semantics, keeping focus on behavior and outcomes.

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 and resource: compiles the project's script modules (plus those of referenced projects) outside the editor into a scratch folder. It also draws the key boundary against the similarly named editor-facing sibling by saying it does not load the change into the editor and that editor_compile does that instead.

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 says 'Use it to find compile errors fast' and names the alternative for the other intent ('for that, use editor_compile'). It also pre-empts the natural exclusion question by noting it works while the editor is open and during play mode.

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