Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

edit_shader

Overwrite an existing Godot shader's GLSL code by supplying its res:// path and new code.

Instructions

Overwrite the GLSL code of an existing 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>",
      "code": "<code>"
    },
    "name": "edit_shader"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesNew shader code
pathYesres:// path to the shader

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/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 discloses that the operation overwrites existing GLSL code, which implies a destructive mutation, but it does not state permission requirements, reversibility, error behavior for missing files, or what the tool returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no redundant or filler wording. It efficiently communicates the core action and target resource.

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?

For a simple two-parameter mutation tool with full schema coverage, the description states the essential purpose and that an existing shader is overwritten. However, with no annotations and no output schema, it leaves behavioral gaps around permissions, failure modes, and return values that an agent might need.

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%, and the schema already documents both parameters: path as a res:// path and code as the new shader code. The description adds no additional meaning, constraints, or formatting details beyond what the schema provides, so the baseline of 3 is appropriate.

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 uses a specific verb, "Overwrite," and a specific resource, "GLSL code of an existing shader file." It clearly states what the tool does, but it does not explicitly distinguish itself from siblings such as create_shader, read_shader, or set_shader_param.

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 explicit guidance on when to use this tool versus alternatives. The phrase "existing shader file" implies it is for replacing code in an already-created shader, but the description does not mention when not to use it or point to related tools like create_shader or set_shader_param.

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