Access shader files in Godot projects to enable AI analysis and editing of visual effects rendering code.
Read shader file. (Compatibility tool)
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "read_shader"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| timeoutMs | No | ||
| autoConnect | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, yet the description discloses nothing about return format, error handling when file doesn't exist, or side effects. The unusual parameter names (timeoutMs, autoConnect) suggest this interacts with a running game/editor instance, but this behavioral context is missing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely brief (two fragments), but the '(Compatibility tool)' text wastes limited space without explaining its significance. Front-loading is adequate, but brevity comes at the cost of necessary detail for the parameter complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of cryptic parameters suggesting network/connection behavior and lack of output schema, the description is insufficient. It fails to explain the Godot-specific context (e.g., reading from Editor vs Filesystem vs Running Game) implied by the parameter names.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description must compensate but mentions neither 'timeoutMs' nor 'autoConnect'. These parameters are semantically cryptic for a file-reading operation and desperately require explanation (e.g., connection timeout vs read timeout).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States basic action ('Read') and resource ('shader file') but fails to distinguish from siblings like 'read_resource' (which could read shaders as resources) or 'edit_shader'. The parenthetical '(Compatibility tool)' is vague and unhelpful for differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides no guidance on when to use this tool versus 'read_resource', 'edit_shader', or 'get_shader_params'. Does not explain what 'Compatibility tool' implies about its use case or when it should be preferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.