Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

delete_file

Remove a specified file from the Godot project filesystem using its res:// path to clean up unused or unwanted assets and scripts.

Instructions

Delete a file from the project filesystem.

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>"
    },
    "name": "delete_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesres:// path of the file to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about irreversibility, trash-vs-permanent deletion, confirmation requirements, or error behavior when the path is missing. For a destructive operation this is a substantial gap; only the target location is disclosed.

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 zero filler. Its brevity is efficient, though it sits close to the line where terseness becomes under-specification for a destructive tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The single parameter is fully documented in the schema and no output schema exists, so the calling mechanics are covered. What is missing is the safety context an agent needs before invoking a delete (irreversibility, failure modes), which matters given zero annotation coverage.

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 the schema already describes 'path' as the res:// path of the file to delete. The description adds no format constraints, path-resolution rules, or examples beyond what the schema supplies, so the baseline of 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?

States a specific verb ('Delete') plus a precisely scoped resource ('a file from the project filesystem'), which naturally distinguishes it from node-oriented siblings like delete_node. It stops short of explicitly naming any sibling as an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'from the project filesystem' implies file-level scope rather than scene-node scope, giving implicit routing guidance. However, there is no explicit when-to-use/when-not guidance, no pointer to batch_delete_nodes for multiple deletions, and no prerequisite notes.

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