Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

list_scenes

List all .tscn scene files in the Godot project. Use it to discover available scenes before inspecting their node trees or generating game code.

Instructions

List all scene files (.tscn) in the project.

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

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?

With no annotations provided, the description carries the full disclosure burden. 'List all' does imply a non-destructive, exhaustive read with no filtering, which is useful, but it says nothing about return shape, whether hidden/generated scenes are included, or whether results are recursive across directories.

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 short sentence with zero waste and the key scoping information ('all', 'in the project') front-loaded. Nothing is padding or restating the tool name verbatim beyond what is needed.

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 trivial zero-parameter tool this is close to adequate, but with no output schema the description never indicates what a result entry looks like (file path vs. scene name) or how results are ordered. That is a modest but real gap an agent would hit on first call.

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 zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly signals the no-argument nature by saying it lists all scenes with no filtering options mentioned.

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 ('scene files (.tscn)'), including the file extension so the resource type is unambiguous. It does not, however, distinguish itself from sibling list tools such as list_scripts or list_animations, so the agent must infer the boundary from the resource name alone.

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 explicit when-to-use guidance, no prerequisites, and no mention of alternatives. The scope word 'in the project' implies it is project-wide rather than per-scene, but the agent gets no stated condition for choosing this over other list_* tools.

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