Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

read_shader

Retrieves the GLSL source code of a Godot shader file from a res:// path so you can inspect and modify shader logic.

Instructions

Read the GLSL source of a 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>"
    },
    "name": "read_shader"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesres:// path to the shader

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 burden of behavioral disclosure. It implies a safe read, but says nothing about error behavior for missing or non-shader paths, whether large shaders are truncated, character encoding, or whether the returned text includes includes/imports resolved — all material for a source-reading 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 short sentence with the verb and object front-loaded and zero filler. It is efficient, though its brevity contributes to the gaps in the other dimensions rather than being purely a virtue.

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 one-parameter read tool with a fully documented schema this is minimally adequate, and 'GLSL source' hints at the return value in the absence of an output schema. Still, nothing covers failure modes or how this differs from generic readers, which an agent needs to select it safely.

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 coverage is 100%, and the schema already documents 'path' as a res:// path to the shader, so the baseline is 3. The description adds only the fact that the target should be a shader file, which is marginal on top of the schema.

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 (Read) and a specific resource (the GLSL source of a shader file), which is enough for an agent to distinguish it from edit_shader, create_shader, or get_shader_params. However, it never names a sibling or explains how it differs from the very similar read_resource / read_script tools.

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 when-to-use or when-not-to-use guidance. With read_resource and read_script in the sibling set, an agent is left to infer that this tool is the shader-specific reader rather than a general file reader, and nothing in the text confirms or rules that out.

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