Skip to main content
Glama
Sign In
godot-mcp-extended

godot-mcp-extended

by daremau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

dotnet_build

Builds the .NET solution or project for a Godot 4.x game, returning structured compiler diagnostics to help fix build errors.

Instructions

Build the .NET solution/project of a Godot 4.x game and return structured compiler diagnostics

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": {
      "projectPath": "<projectPath>"
    },
    "name": "dotnet_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoOptional: specific .sln or .csproj file name within the project directory
projectPathYesPath to the Godot project directory
configurationNoOptional: MSBuild configuration, Debug or Release (defaults to Release)
maxDiagnosticsNoOptional: maximum diagnostics to return (defaults to 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose that the tool returns structured compiler diagnostics, which is genuinely useful, but says nothing about side effects (writing bin/obj artifacts), failure behavior on compile errors, or required permissions/SDK.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though it is terse enough that some required context is absent rather than trimmed.

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?

With four parameters, no annotations, and no output schema, the description should do more. It covers purpose and the diagnostic return shape, but omits build prerequisites, side effects, and error/failure semantics that an agent needs before invoking a build command.

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 all four parameters (projectPath, target, configuration, maxDiagnostics) are already documented with defaults and enum-like values in the schema. The description adds no parameter 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Build') and resource ('.NET solution/project') scoped to Godot 4.x games, plus the return payload (structured compiler diagnostics). It is naturally distinguishable from the sibling dotnet_test, but it never explicitly differentiates itself from that or any other sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites (e.g. the project must be a .NET-enabled Godot project), and no mention of alternatives such as dotnet_test for running tests. The agent must infer the invocation context entirely.

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

Deploy Server

Other Tools