Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

analyze_scene_complexity

Analyze a Godot scene to report node count, depth, script count, and other complexity metrics, helping you identify heavy scenes before optimization.

Instructions

Analyze a scene and report node count, depth, script count, and other complexity metrics.

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

Input Schema

NameRequiredDescriptionDefault
scene_pathNores:// path to the scene (default: current scene)

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, the description carries the full behavioral burden. It usefully discloses the reported metrics, implying a read-only analysis operation, but it does not explicitly state that it is non-mutating or describe error behavior.

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 front-loaded sentence with no filler. It names the action and the key metrics efficiently.

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 one-parameter analysis tool with no output schema, the description gives enough context to understand the purpose and reported metrics. It is nearly complete, though it could be slightly stronger by clarifying that it does not mutate the scene.

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 coverage is 100%, so the schema already documents the scene_path parameter and its default current-scene behavior. The description only says 'a scene' and adds no extra parameter meaning beyond that.

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 states a clear verb and resource: analyze a scene and report specific complexity metrics. It is understandable without opening the schema, but it does not explicitly distinguish itself from similarly named siblings like analyze_code_complexity.

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 gives no when-to-use guidance, prerequisites, or alternatives. It does not explain when an agent should choose this over analyze_code_complexity or other scene inspection 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