Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_shader_param

Updates a shader uniform value on a node's ShaderMaterial by node path and parameter name, letting AI edit material visuals in Godot without manual inspector changes.

Instructions

Set a shader uniform parameter on a node's ShaderMaterial.

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>",
      "param_name": "<param_name>",
      "value": "<value>"
    },
    "name": "set_shader_param"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesValue to set
node_pathYesNode path
param_nameYesUniform parameter name

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 supplied, so the description carries the full disclosure burden. Beyond the word "Set" it says nothing about whether the material must already exist, what happens with an unknown uniform name, whether values are validated/coerced per uniform type, whether the change is persistent or requires a save, or whether the shader recompiles — all significant for a mutation tool.

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, which is well-sized for a three-parameter tool. The brevity is efficient but edges toward under-specification rather than tight completeness.

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 three-parameter mutation with full schema coverage and no output schema, the definition is minimally adequate. It is missing the prerequisites and failure behavior that matter most when no annotations are present to describe the mutation's risk profile.

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% (node_path, param_name, value all documented), so the baseline is 3. The description adds only the framing that param_name refers to a shader uniform and node_path refers to a node with a ShaderMaterial; it adds no format guidance for path syntax or value typing per uniform.

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 ("Set") and resource ("shader uniform parameter") scoped to "a node's ShaderMaterial", which is much more informative than the bare name. It does not explicitly distinguish itself from nearby siblings such as set_material_3d or get_shader_params, so differentiation is left to inference.

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 stated prerequisite that the node must already have a ShaderMaterial assigned, and no mention of related tools (e.g. get_shader_params to discover valid uniform names, or assign_shader_material to attach one first). The agent must guess the workflow context.

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