Skip to main content
Glama
Sign In
Godot MCP Server Ultimate Edition

Godot MCP Server Ultimate Edition

by Dex865378
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_shader

Generate a new .gdshader file with custom source code for a Godot project, using the project path and shader path relative to the project.

Instructions

Create a Godot shader file (.gdshader) with content

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>",
      "shaderPath": "<shaderPath>",
      "content": "<content>"
    },
    "name": "create_shader"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYes
shaderPathYesShader path relative to project (e.g. shaders/glow.gdshader)
contentYesFull shader source code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It states 'Create' which implies file creation, but does not mention side effects like overwriting existing files, file permission requirements, or whether the content must be valid .gdshader syntax. The description adds minimal behavioral context beyond the obvious.

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?

The description is a single sentence with no unnecessary words. It is front-loaded with the key action. However, it could be more informative without adding length, such as including the requirement for valid .gdshader content.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and the tool's low complexity (3 required params, no nested objects), the description should explain what happens after creation (e.g., returns success, file path). It does not address this, leaving the agent uncertain about the tool's outcome. The description is incomplete for safe autonomous use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67%, with two out of three parameters (shaderPath and content) having descriptions in the schema. However, the overall description 'with content' does not add meaning beyond the schema. For the parameter projectPath, which lacks a schema description, the tool description provides no clarification. The value added is low.

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?

The description clearly states the action ('Create') and the specific resource ('Godot shader file (.gdshader)'). This differentiates it from sibling tools like create_script, which creates GDScript files. The verb-resource combination is distinct and unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., create_script for scripts, or other file creation tools). There is no mention of prerequisites, conditions for use, or when not to use it. The agent is left to infer usage from the name alone.

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