Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_material_3d

Create and assign a StandardMaterial3D or BaseMaterial3D to a MeshInstance3D, setting material properties so AI-driven Godot workflows can apply shading to 3D mesh nodes.

Instructions

Create and assign a StandardMaterial3D (or BaseMaterial3D) to a MeshInstance3D.

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>"
    },
    "name": "set_material_3d"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesNode path of the MeshInstance3D
propertiesNoMaterial property values
material_typeNoMaterial class (default: StandardMaterial3D)

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 provided, the description carries the full burden. It implies a mutation and resource creation but says nothing about whether an existing material on the node is replaced, whether the created material is shared or unique, whether the node_path must resolve to an existing MeshInstance3D, or what errors occur 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 wasted words. It is efficient, though its brevity reflects under-specification rather than deliberate compression.

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 three-parameter mutation tool with a nested free-form 'properties' object, no annotations, and no output schema, the description leaves too much unexplained. In particular, an agent has no way to learn which material properties are accepted or what the tool returns.

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%, so all three parameters are already documented in structured form, and the description only restates the material_type default already present in the schema. It adds no meaning beyond the schema, particularly for the free-form nested 'properties' object.

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 pair (create and assign) plus a concrete resource (StandardMaterial3D/BaseMaterial3D) and target (MeshInstance3D), which is enough to distinguish it from sibling set_particle_material. It stops short of explicitly contrasting itself with assign_shader_material, which also touches materials.

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 or when-not-to-use guidance, no mention of assign_shader_material or set_particle_material as alternatives, and no prerequisites such as whether the node must already exist. The agent must infer selection and ordering on its own.

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