Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

search_files

Find files by glob or substring pattern within a Godot project, with an optional root path to scope the results.

Instructions

Search for files matching a pattern inside the project.

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": {
      "pattern": "<pattern>"
    },
    "name": "search_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoRoot path to search from (default: res://)
patternYesGlob or substring pattern to match file names

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does not disclose whether the search is recursive, case-sensitive, whether it matches directories, whether results are paths or objects, or any limits on result count — only that matching happens 'inside the project'.

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 sentence with no wasted words, front-loading the action and resource. It is efficient, though the brevity comes at the cost of the missing behavioral detail rather than being a deliberate compression of richer content.

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?

This is a simple two-parameter read tool with a fully documented schema and no output schema, so the description does not need to explain return values. However, with zero annotation coverage, nothing is said about safety profile or result format, leaving a modest gap for even a simple search tool.

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 both parameters are already documented, and the description adds no format or syntax detail beyond what the schema states. Baseline 3 is appropriate when the 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?

States a specific verb and resource ('search for files') plus the scoping qualifier 'inside the project' and the matching criterion (a pattern). It is clear enough to distinguish from mutation tools like add_node or batch_add_nodes, but it does not explicitly contrast with any other search/inspection sibling.

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 offers no when-to-use or when-not-to-use guidance and names no alternative. An agent must infer usage purely from the verb 'search', with nothing about whether to reach for it versus listing nodes or analyzing the scene.

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