Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

assign_shader_material

Assign a shader as a ShaderMaterial to a Godot node using its node path and shader file path, enabling custom rendering effects without manual material setup.

Instructions

Assign a shader (as a ShaderMaterial) to a node.

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": {
      "node_path": "<node_path>",
      "shader_path": "<shader_path>"
    },
    "name": "assign_shader_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesNode path to assign the material to
shader_pathYesres:// path to the shader file

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?

No annotations are provided, so the description carries the full behavioral burden. It hints that the shader is instantiated as a ShaderMaterial, but says nothing about whether an existing material is overwritten, whether the shader path is validated, what permissions are needed, or what the response looks like on failure.

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; the parenthetical about ShaderMaterial is the one piece of information worth its space. It is perhaps too terse, but nothing is wasted.

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 two-parameter tool with full schema coverage and no output schema, the description covers the core action adequately. It falls short on mutation semantics (overwrite behavior, error cases) that would matter for a write operation with no annotations to back it up.

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 both node_path and shader_path documented in the schema itself. The description adds no meaning beyond those fields (e.g., path format quirks, relative vs absolute resolution), 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?

States a specific verb and resource ('Assign a shader ... to a node') and adds a useful detail that the shader is wrapped as a ShaderMaterial. However, it never distinguishes itself from siblings like set_material_3d or set_particle_material, which an agent could easily confuse with this tool.

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 guidance on when to use this versus set_material_3d, set_particle_material, or create_shader. The agent must infer that this is the shader-specific path, and no prerequisites (e.g., node must exist, shader file must exist) 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