Skip to main content
Glama

folder_create

Create new folders in Unity projects to organize assets and scripts. Specify the path to add structure to your project directory.

Instructions

Create a new folder in Unity project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath for the new folder (e.g., Assets/MyFolder)

Implementation Reference

  • The main handler for the 'folder_create' tool in the executeTool method's switch statement. It validates the required 'path' parameter, calls the adapter's createFolder method, and returns a formatted success message with the created folder's path and GUID.
    case 'folder_create': {
      if (!args.path) {
        throw new Error('path is required');
      }
      const result = await this.adapter.createFolder(args.path);
      return {
        content: [{
          type: 'text',
          text: `Folder created successfully:\nPath: ${result.path}\nGUID: ${result.guid}`
        }]
      };
    }
  • Registration of the 'folder_create' tool in the getTools() method, defining its name, description, and input schema requiring a 'path' parameter.
    {
      name: 'folder_create',
      description: 'Create a new folder in Unity project',
      inputSchema: {
        type: 'object',
        properties: {
          path: {
            type: 'string',
            description: 'Path for the new folder (e.g., Assets/MyFolder)'
          }
        },
        required: ['path']
      }
    },
  • Supporting method in UnityHttpAdapter that implements the folder creation by calling the Unity HTTP server's 'folder/create' endpoint via the generic call() method.
    async createFolder(path: string): Promise<{ path: string; guid: string }> {
      return this.call('folder/create', { 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 this is a creation operation but doesn't mention permission requirements, whether it overwrites existing folders, error conditions, or what happens on success. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that states the core purpose without any wasted words. It's appropriately sized for a simple creation tool and front-loads the essential information.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation, what gets returned, error conditions, or permissions needed. Given the complexity of file system operations and the lack of structured safety information, more 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%, so the schema already documents the single 'path' parameter. The description doesn't add any parameter-specific information beyond what's in the schema. The baseline of 3 is appropriate when the schema does the heavy lifting for parameter documentation.

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 ('Create') and target resource ('a new folder in Unity project'), making the purpose immediately understandable. It doesn't specifically differentiate from sibling tools like folder_move or folder_rename, but the verb 'Create' is distinct enough from their operations.

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 folder_move or folder_rename. There's no mention of prerequisites, constraints, or typical use cases. The agent must infer usage from the tool name alone.

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