Skip to main content
Glama
Sign In
Godot MCP Server Ultimate Edition

Godot MCP Server Ultimate Edition

by Dex865378
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_scene_backups

List available backups for a Godot scene file, ordered by most recent, to review restore points before restoring a backup.

Instructions

List all available backups for a scene file, ordered by most recent first. Use this to review available restore points before calling restore_scene_backup.

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": {
      "projectPath": "<projectPath>",
      "scenePath": "<scenePath>"
    },
    "name": "list_scene_backups"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYesPath to the Godot project directory
scenePathYesScene path relative to project (e.g. scenes/level.tscn)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses the ordering behavior ('most recent first') but does not mention potential empty results or rate limits. However, for a read-only list operation, this is adequate.

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?

Two concise sentences with zero waste. The main purpose is front-loaded, and the usage guideline is efficiently appended.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with two string parameters and no output schema, the description covers purpose and usage. It lacks specification of the return format (e.g., list of names/paths), but this is a minor gap given the simplicity.

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% with clear parameter descriptions. The tool description adds no additional semantic value beyond the schema, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'List' and the resource 'backups for a scene file', and specifies ordering by most recent. It distinguishes from sibling tools like 'restore_scene_backup' and 'backup_scene'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool: 'before calling restore_scene_backup', providing a clear usage context and linking to a related sibling tool.

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