Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

find_unused_resources

Identifies resource files in a Godot project that are not referenced by any scene or script, helping clean up unused assets.

Instructions

Find resource files in the project that are not referenced by any scene or script.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_unused_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoRoot path to search (default: res://)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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 and does not meet it. It never states that the operation is read-only, whether the scan can be slow on large projects, how 'referenced' is determined (scene text, resource dependencies, script paths), or what the caller receives back. Only the core semantics of 'unreferenced' are conveyed.

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?

One sentence, front-loaded with the verb and the constraint, with no filler or redundant restatement of the title. Nothing could be cut without losing meaning.

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?

For a single-parameter, likely read-only analysis tool this covers the what, but with no annotations and no output schema the description should also say it is non-destructive and roughly what it returns. The 'not referenced' definition, the most important semantic, is left unqualified.

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 single 'path' parameter is fully documented with its default of res://, so the baseline of 3 applies. The description adds only the vague phrase 'in the project' and no syntax hints, scoping rules, or behavior for paths outside res://.

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 names a specific verb ('Find') and resource ('resource files in the project') plus the defining criterion: 'not referenced by any scene or script'. That makes the operation concrete. It stops short of contrasting with look-alike siblings such as find_missing_references (the inverse direction), so the agent must infer the distinction.

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?

Usage is only implied by the purpose statement: an agent can guess this is for project cleanup or dead-asset detection. There is no explicit 'use when' trigger, no exclusions, and no named alternative for the related case of finding missing references. Adequate but leaves routing to inference.

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