Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

create_shader

Creates a new Godot shader file at a specified res:// path, with optional GLSL code and shader type, enabling shader assets to be added to a project.

Instructions

Create a new shader file.

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": {
      "path": "<path>"
    },
    "name": "create_shader"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoInitial GLSL shader code
pathYesres:// path for the shader file
typeNoShader type (spatial, canvas_item, particles)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, and it says nothing about overwrite behavior if the path already exists, whether the parent directory must exist, what the default shader type is, or what is returned. A mutation tool on a filesystem needs at least the existence/overwrite semantics spelled out.

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 but arguably too terse for a file-creating operation, leaving no room for the behavioral caveats that would earn a higher contextual score.

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?

For a mutation tool with no annotations and no output schema, the description should at least state overwrite semantics and any path constraints; the schema covers the parameters fully but says nothing about effects. The agent is left guessing what happens on collision or missing directories.

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%, with each of the three properties documented including enum-like values for type (spatial, canvas_item, particles) and the res:// path convention. The description adds no meaning beyond that, so the baseline of 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 gives a specific verb and resource ("Create a new shader file"), so the agent knows exactly what operation is performed. It does not, however, distinguish this from siblings such as edit_shader or create_script, which is the only thing separating a 4 from a 5 here.

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 statement of when to use this versus edit_shader for an existing shader, or versus create_resource. The agent must infer from the name alone that this is for new files, and no prerequisites or alternatives are mentioned.

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