Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

edit_resource

Update properties of an existing Godot Resource file by passing its res:// path and property-value pairs.

Instructions

Update properties of an existing Godot Resource file.

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": {
      "path": "<path>",
      "properties": "<properties>"
    },
    "name": "edit_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesres:// path to the resource
propertiesYesProperty name→value pairs to update

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?

With no annotations supplied, the description carries the full burden and delivers little: it does not say whether changes are written to disk immediately, whether unspecified properties are preserved, whether unknown property names error out, or whether the operation is reversible. For a mutation tool this is a significant gap.

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?

A single front-loaded sentence with no filler. It is efficient, though the terseness borders on under-specification given the nested arbitrary-key parameter.

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?

The tool takes an open-ended property map with nested objects and no annotations or output schema, yet the description says nothing about discovering valid property names, error behavior, or result reporting. An agent could not reliably call this correctly without trial and error.

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 coverage is 100% and both parameters are documented there, so the baseline of 3 applies. The description adds nothing beyond the schema — it does not explain what property names are valid or how values are typed/coerced for the nested properties object.

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?

States a specific verb (Update) and target (properties of an existing Godot Resource file), which implicitly separates it from edit_script and edit_shader. It stops short of explicitly differentiating itself from create_resource or of noting what a 'Resource file' covers, so it is clear but not maximally disambiguating.

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?

No guidance on when to use this versus create_resource, read_resource, or get_resource_preview, and no prerequisites such as the resource needing to exist or the editor needing it open. The agent must infer usage entirely from the name and the word 'existing'.

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