Skip to main content
Glama

shader_read

Read shader files from Unity projects to access and analyze shader code for development, debugging, or integration purposes.

Instructions

Read a shader from Unity project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the shader file

Implementation Reference

  • Handler for the shader_read tool. Validates path argument, calls UnityHttpAdapter.readShader, and formats the shader content in the tool response.
    case 'shader_read': {
      if (!args.path) {
        throw new Error('path is required');
      }
      const result = await this.adapter.readShader(args.path);
      return {
        content: [{
          type: 'text',
          text: `Shader content from ${result.path}:\n\n${result.content}`
        }]
      };
    }
  • Tool schema definition including name, description, and input validation requiring a 'path' parameter.
    {
      name: 'shader_read',
      description: 'Read a shader from Unity project',
      inputSchema: {
        type: 'object',
        properties: {
          path: {
            type: 'string',
            description: 'Path to the shader file'
          }
        },
        required: ['path']
      }
    },
  • Adapter helper method that sends HTTP POST request to Unity MCP server endpoint 'shader/read' with the file path.
    async readShader(path: string): Promise<any> {
      return this.call('shader/read', { path });
    }
  • Registration of the shader_read tool in the getTools() method's return array.
    {
      name: 'shader_read',
      description: 'Read a shader from Unity project',
      inputSchema: {
        type: 'object',
        properties: {
          path: {
            type: 'string',
            description: 'Path to the shader file'
          }
        },
        required: ['path']
      }
    },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Read' which implies a read operation, but doesn't specify whether this requires specific permissions, what happens if the path doesn't exist, or what format the output takes. For a tool with zero annotation coverage, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a simple read operation and gets straight to the point without unnecessary elaboration.

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 read operation with no annotations and no output schema, the description should provide more context about what 'read' entails - what data is returned, in what format, and any constraints. The current description is too minimal given the lack of structured information elsewhere.

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 the schema already documents the single 'path' parameter. The description doesn't add any additional meaning about the parameter beyond what the schema provides (e.g., path format, relative vs absolute paths). Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the action ('Read') and resource ('a shader from Unity project'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'script_read' or 'shader_create', but the verb+resource combination is specific enough for basic understanding.

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?

The description provides no guidance on when to use this tool versus alternatives like 'script_read' or 'shader_create', nor does it mention prerequisites or context for usage. It simply states what the tool does without any usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zabaglione/mcp-server-unity'

If you have feedback or need assistance with the MCP directory API, please join our Discord server