Skip to main content
Glama

find_scene_instances

Locate all scenes that use a specific scene in Godot projects, showing parent node paths for dependency tracking and project analysis.

Instructions

Find all scenes that instance (use) a given scene, with parent node paths.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneYesPath to the scene to search for instances of
maxResultsNoMaximum results to return

Implementation Reference

  • The handler for the 'find_scene_instances' tool, which searches for scene instances in the index and handles path formatting.
      handler: async (ctx) => {
        const { scene, maxResults = 20 } = ctx.args;
        validatePath(scene);
    
        let results = await index.findSceneInstances(scene);
        // instanceRefs are keyed by res:// paths; try res:// form too
        if (results.length === 0 && projectRoot) {
          const resPath = absoluteToRes(scene, projectRoot);
          results = await index.findSceneInstances(resPath);
        }
        const truncated = results.length > maxResults;
        return makeTextResponse({
          data: results.slice(0, maxResults),
          truncated,
          totalCount: results.length,
          metadata: { source: "index" },
        });
      },
    },
  • Tool registration for 'find_scene_instances' including name, description, and schema.
    name: "find_scene_instances",
    description: "Find all scenes that instance (use) a given scene, with parent node paths.",
    schema: {
      scene: z.string().describe("Path to the scene to search for instances of"),
      maxResults: z
        .number()
        .int()
        .min(1)
        .max(500)
        .optional()
        .default(20)
        .describe("Maximum results to return"),
    },
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 burden. It mentions the tool returns 'parent node paths,' which adds some behavioral context, but lacks details on permissions, rate limits, error handling, or whether it's read-only/destructive. For a search tool with zero annotation coverage, this is insufficient.

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?

The description is a single, efficient sentence that front-loads the core functionality. It wastes no words and directly communicates the tool's purpose and output, making it easy to parse quickly.

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?

Given no annotations and no output schema, the description is minimal but covers the basic purpose. It doesn't explain return values (e.g., format of 'parent node paths'), error cases, or behavioral constraints. For a search tool with 2 parameters, this is adequate but leaves gaps in understanding how to interpret results.

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%, so the schema fully documents both parameters ('scene' and 'maxResults'). The description doesn't add any parameter-specific details beyond what's in the schema, such as format examples for 'scene' or usage tips for 'maxResults.' Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the tool's purpose: 'Find all scenes that instance (use) a given scene, with parent node paths.' It specifies the verb ('Find'), resource ('scenes'), and what it returns ('parent node paths'). However, it doesn't explicitly differentiate from siblings like 'find_references' or 'get_scene_dependencies', which might have overlapping functionality.

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 is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, exclusions, or compare it to sibling tools like 'find_references' or 'get_scene_dependencies' that might serve similar purposes. Usage context is implied but not explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/woohq/godette-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server