Skip to main content
Glama

find_resource

Search for specific resource types within Godot projects to locate assets like ShaderMaterial files across indexed content.

Instructions

Find resources by type across the indexed project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesResource type to search for (e.g. 'ShaderMaterial')
maxResultsNoMaximum results to return

Implementation Reference

  • Handler for the find_resource tool which queries the resourceIndex by type.
    handler: async (ctx) => {
      const { type, maxResults = 50 } = ctx.args;
      const results = await index.resourceIndex.findByType(type);
      const truncated = results.length > maxResults;
      const data = results.slice(0, maxResults).map((r) => ({
        filePath: r.filePath,
        type: r.type,
        properties: Object.keys(r.properties),
        externalDeps: r.externalDeps,
      }));
    
      return makeTextResponse({
        data,
        truncated,
        totalCount: results.length,
        metadata: { source: "index" },
      });
    },
  • Input schema for find_resource defining type and maxResults parameters.
    schema: {
      type: z.string().describe("Resource type to search for (e.g. 'ShaderMaterial')"),
      maxResults: z
        .number()
        .int()
        .min(1)
        .max(500)
        .optional()
        .default(50)
        .describe("Maximum results to return"),
    },
  • Tool registration for find_resource in createResourceTools.
    {
      name: "find_resource",
      description: "Find resources by type across the indexed project.",
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions 'across the indexed project' which provides some context about scope, but doesn't describe what 'indexed' means, whether this is a read-only operation, what format results are returned in, or any performance/rate limit considerations. For a search tool with zero annotation coverage, this is inadequate.

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 gets straight to the point with zero wasted words. It's appropriately sized for a simple search tool and front-loads the essential information about what the tool does.

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?

For a search tool with no annotations and no output schema, the description is insufficient. It doesn't explain what constitutes a 'resource', what 'indexed' means, what format results are returned in, or how this differs from similar sibling tools. Given the complexity of having multiple find-related tools and no structured output documentation, the description should provide more contextual guidance.

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 already fully documents both parameters. The description doesn't add any meaningful parameter semantics beyond what's in the schema - it doesn't explain what 'type' values are valid beyond the example in the schema, or provide context about how the search works. Baseline 3 is appropriate when the schema does all the work.

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 action ('Find') and target ('resources by type across the indexed project'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from similar sibling tools like 'find_resources_of_type' or 'find_file', which could cause confusion about when to use this tool versus those alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives. With multiple 'find'-prefixed sibling tools (e.g., find_resources_of_type, find_file, find_node), there's no indication of when this general 'find_resource' is preferred over more specific tools or what distinguishes its functionality from them.

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