Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

create_resource

Creates a new Godot Resource file of a specified type at a res:// path, with optional initial property values for setup.

Instructions

Create a new Godot Resource file of the given type.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "path": "<path>"
    },
    "name": "create_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesres:// path to save the resource
typeYesResource class (e.g. Environment, PhysicsMaterial)
propertiesNoInitial property values

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden yet discloses almost nothing beyond the mutation itself. It does not state what happens if the path already exists (overwrite vs error), whether the parent directory must already exist, whether the file is written to disk immediately, or what the response contains.

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?

A single front-loaded sentence with zero filler that identifies the action and target immediately. Nothing in it is redundant or padded.

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 leaves key operational questions unanswered: overwrite semantics for an existing path, directory preconditions, and how the nested properties object is applied. Given nested-object input and disk-writing behavior, it should say considerably more.

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 each of the three parameters documented inline (res:// path, resource class examples, initial property values), so the schema does the heavy lifting. The description adds no extra meaning about how type, path, and properties interact at creation time; baseline 3 applies.

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?

"Create a new Godot Resource file of the given type" gives a specific verb (create) plus resource (Godot Resource file) and implies scope (new, not existing). It is clear what the tool does, but it never names or contrasts with siblings such as edit_resource or create_scene, so differentiation is left to inference.

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 word "new" hints that this is for resources that do not yet exist, but there is no explicit when-to-use, when-not-to-use, or pointer to edit_resource for modifying existing resources. The agent must infer the create-vs-edit boundary from the name alone.

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

Deploy Server

Other Tools