Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_shader_params

Retrieves all shader uniform parameters from a node's ShaderMaterial so you can inspect and modify shader values in Godot.

Instructions

Get all shader uniform parameters from 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>"
    },
    "name": "get_shader_params"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesNode path

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 behavioral burden. It implies a read through the verb 'Get' and the word 'all' suggests an unfiltered dump, but it says nothing about what happens when the node has no ShaderMaterial assigned, whether that errors or returns empty, or the format of the returned parameters.

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, correctly sizing the explanation for a one-parameter read tool. It is efficient but leaves little room for the missing qualifiers noted in other dimensions.

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 one-parameter read tool with full schema coverage, this is close to adequate. However, with no output schema the description should at least characterize the returned structure or the no-material failure case, and it does neither.

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?

There is a single parameter at 100% schema coverage, so the schema baseline applies. The description does add one useful constraint the schema lacks: node_path must point at a node that actually has a ShaderMaterial, since the params are read from that material.

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: 'Get all shader uniform parameters' scoped to 'a node's ShaderMaterial'. That scope distinguishes it reasonably from generic readers like get_node_properties or read_shader, though it never names an alternative explicitly.

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 prerequisites, and no mention of alternatives. An agent is told what the tool returns but not the situation that should select it over read_shader or get_node_properties.

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