Skip to main content
Glama
Beckett — MCP for Godot

Beckett — MCP for Godot

by beckettlab

build_csharp

Read-only

Compile-check a C#/.NET Godot project after editing .cs files, returning structured diagnostics with file, line, column, and CS codes. Runs an isolated build so the editor's loaded assembly stays untouched.

Instructions

Compile-check a C#/.NET Godot project with dotnet build, returning structured diagnostics (errors/warnings with file:line:col + CS-code). Isolated build (scratch output) — never touches the editor's loaded assembly, so it's safe while the editor is open. Auto-detects the .csproj if omitted. Needs the .NET SDK, checked first (Godot 4.8 needs SDK 10): a missing or too-old one comes back as a plain error saying what to install, not as build noise. First build restores packages (slower); incremental ~1-3s. Use after editing .cs — the GDScript compile-gate (write_script) does NOT cover C#.

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

Input Schema

NameRequiredDescriptionDefault
csprojNores:// or absolute path to the .csproj; auto-detected from the project if omitted
configurationNoDebug (default) or Release

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.1
  2. Removedv1.10.0
  3. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnly/destructive annotations: isolated scratch-output build that never touches the editor's loaded assembly, SDK presence/version check surfacing as a plain error rather than build noise, and timing expectations (slower first build due to restore, ~1-3s incremental). These are real behavioral traits an agent cannot get from the annotations.

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 purpose and return value, then layered with safety, prerequisite, and timing details; every sentence carries information. It is dense but not padded, though it runs slightly long as a single block.

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?

There is no output schema, yet the description explains the diagnostics format so an agent knows what comes back. It also covers prerequisites and failure modes (SDK missing/too old). Minor gap: no mention of whether warnings fail the build or how errors are surfaced for non-C# projects.

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 coverage is 100%, so both `csproj` and `configuration` are already documented in the schema. The description only restates the auto-detect behavior for `csproj` and adds nothing about `configuration` defaults, 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 and resource ('Compile-check a C#/.NET Godot project with `dotnet build`') plus the return shape (structured errors/warnings with file:line:col + CS-code). It distinguishes itself from the GDScript compile path used by write_script, so an agent can tell it apart from the many scene/script siblings.

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 after editing .cs' and warns that the GDScript compile-gate (write_script) does NOT cover C#, which is exactly the routing decision an agent needs. It also gives the prerequisite (.NET SDK, checked first) and the condition under which it is safe (editor open).

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