Skip to main content
Glama

create_file

Create new files with specified content in Godot projects to manage game development assets and trigger automatic indexing updates.

Instructions

Create a new file with the given content. Triggers index update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath for the new file
contentYesFile content

Implementation Reference

  • The handler for the 'create_file' tool, which creates a file and emits a file:changed event.
      name: "create_file",
      description: "Create a new file with the given content. Triggers index update.",
      schema: {
        path: z.string().describe("Path for the new file"),
        content: z.string().describe("File content"),
      },
      handler: async (ctx) => {
        const { path, content } = ctx.args;
        validatePath(path);
        try {
          const dir = dirname(path);
          if (!existsSync(dir)) {
            mkdirSync(dir, { recursive: true });
          }
    
          writeFileSync(path, content, "utf-8");
    
          await eventBus.emit("file:changed", {
            path,
            type: "created",
          });
    
          return makeTextResponse({
            data: { path, size: content.length },
            metadata: { source: "fallback" },
          });
        } catch (err) {
          return makeTextResponse({
            error: `Failed to create file: ${(err as Error).message}`,
            data: null,
          });
        }
      },
    },
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 mentions that the tool 'triggers index update', which is valuable context about side effects. However, it doesn't address important behavioral aspects like whether the tool overwrites existing files, what permissions are required, error conditions, or what happens on failure.

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?

The description is appropriately concise with two sentences that each add value. The first sentence states the core functionality, and the second adds important behavioral context about index updates. There's no wasted verbiage or repetition.

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 file creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens if a file already exists at the path, what format the path should use, what permissions are needed, what the return value is, or how errors are handled. The mention of index update is helpful but doesn't compensate for these significant gaps.

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 fully documents both parameters. The description adds no additional parameter semantics beyond what's in the schema. It mentions 'with the given content' which aligns with the 'content' parameter, but provides no extra context about parameter usage, constraints, or examples.

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 tool's purpose with a specific verb ('Create') and resource ('new file'), and mentions content creation. However, it doesn't explicitly differentiate from sibling tools like 'replace_content' or 'insert_at_line' that also modify files, leaving some ambiguity about when this specific creation tool should be chosen over alternatives.

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 'replace_content' or 'insert_at_line'. It mentions that it 'triggers index update', which hints at a side effect, but doesn't explain when this tool is appropriate versus other file modification tools in the sibling list.

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/woohq/godette-mcp'

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