Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

list_scripts

Lists all GDScript files in a Godot project or under a specified path, helping you locate scripts for debugging, refactoring, or code generation.

Instructions

List all GDScript files in the project (or under a specific path).

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": "list_scripts"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 disclosure burden alone. It implies a read-only recursive scan rooted at the project path, but does not say whether it recurses, whether it skips addons/.godot caches, or what form results take. The implicit read-only nature keeps this from being worse than a 3.

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 short sentence, front-loaded with the verb and resource, with the scoping variant parenthesized rather than buried. Nothing is redundant or padding.

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 one-optional-param read-only lister with full schema coverage and no output schema, the definition is close to sufficient. It still omits recursion behavior and the shape of the returned file list, which an agent would want before relying on 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% and the single optional path parameter already documents its default of res://. The description adds only that the path acts as a search root, which is marginal beyond the schema, so the baseline 3 applies.

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 ("List") and a specific resource ("GDScript files") with its scope (project-wide or under a given path). That is enough for an agent to distinguish it from siblings such as list_scenes or list_animations without opening a schema, though it never explicitly names a contrasting tool.

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: the parenthetical "(or under a specific path)" hints that a path narrows the search, but there is no statement of when to prefer this tool over other listing tools or what to do if no GDScript files exist. Adequate for a simple read-only lister, not instructive.

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