Skip to main content
Glama

script_delete

Remove C# script files from Unity projects to clean up unused code and manage project structure.

Instructions

Delete a C# script from Unity project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the script file

Implementation Reference

  • Handler for the 'script_delete' tool. Validates the 'path' argument and calls UnityHttpAdapter.deleteScript(path) to perform the deletion, then returns success message.
    case 'script_delete': {
      if (!args.path) {
        throw new Error('path is required');
      }
      await this.adapter.deleteScript(args.path);
      return {
        content: [{
          type: 'text',
          text: `Script deleted successfully: ${args.path}`
        }]
      };
    }
  • Schema definition and registration for the 'script_delete' tool, specifying input requirements (path: string).
    {
      name: 'script_delete',
      description: 'Delete a C# script from Unity project',
      inputSchema: {
        type: 'object',
        properties: {
          path: {
            type: 'string',
            description: 'Path to the script file'
          }
        },
        required: ['path']
      }
    },
  • Helper method in UnityHttpAdapter that implements script deletion by calling the Unity HTTP endpoint 'script/delete' with the path.
    async deleteScript(path: string): Promise<any> {
      return this.call('script/delete', { 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. While 'Delete' implies a destructive operation, it doesn't specify whether deletion is permanent, reversible, requires confirmation, affects dependencies, or has any rate limits. This is a significant gap for a destructive operation with zero annotation coverage.

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 deletion tool and front-loads the essential information 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 destructive deletion tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after deletion, whether the operation is atomic, what errors might occur, or what the return value might be. Given the complexity of file deletion in a project context, more behavioral context is needed.

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% with the single 'path' parameter fully documented in the schema. The description doesn't add any additional parameter context beyond what the schema provides, such as path format examples or constraints. Baseline 3 is appropriate when the 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 ('Delete') and the resource ('a C# script from Unity project'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'shader_delete' or 'folder_delete', but the specificity of 'C# script' provides some differentiation.

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 'shader_delete' or 'folder_delete'. It doesn't mention prerequisites, consequences, or when this operation is appropriate versus other deletion tools in the sibling set.

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