Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

find_missing_references

Detect broken or missing resource references in the current Godot scene so you can locate and fix dependency issues before they cause errors.

Instructions

Find broken/missing resource references in the current scene.

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_missing_references"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the whole burden. The word 'Find' implies a read-only scan, but nothing states whether the tool repairs anything, what it returns (a list, a count, a report), or how it handles a scene with no problems. For a zero-parameter inspector the risk is low, so this is adequate but incomplete.

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 sentence with zero filler, front-loaded with the verb and the scope. Nothing is repeated from the name needlessly and there is no trailing qualification to parse.

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?

With no annotations and no output schema, the definition should at least sketch the shape of the result and confirm the operation is non-destructive. For a simple no-argument scan it is close to sufficient, but the return-value behavior is entirely undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, which is the baseline-4 case. The description is consistent with that, adding only the implicit operand (the current scene) rather than inventing inputs the schema does not have.

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 gives a specific verb and resource ('Find broken/missing resource references') plus an explicit scope ('in the current scene'), so an agent knows exactly what it scans. It falls short of 5 because it does not distinguish itself from a close sibling like find_unused_resources, leaving the boundary between 'missing' and 'unused' 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?

There is no when-to-use guidance, no prerequisites, and no named alternative or exclusion. The scope phrase 'in the current scene' tells the agent where it operates, not when it should be preferred over related lookups such as find_unused_resources.

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