Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

analyze_code_complexity

Analyze a GDScript file to report cyclomatic complexity, function count, and line count, helping you identify complex code and target refactoring.

Instructions

Analyze a GDScript file and report cyclomatic complexity, function count, line count, etc.

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": {
      "script_path": "<script_path>"
    },
    "name": "analyze_code_complexity"
  }
}

Input Schema

NameRequiredDescriptionDefault
script_pathYesres:// path to the script

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 implies a read-only analysis and lists examples of reported metrics, but it does not cover error behavior, parsing limits, or the precise response format.

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?

The description is a single front-loaded sentence with no unnecessary setup. The trailing "etc." slightly weakens precision but does not undermine conciseness.

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 simple one-parameter analyzer, the description is mostly sufficient: it identifies the input type and examples of outputs. It is less complete because there is no output schema and the return shape is only partially indicated by "etc."

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%, and the single script_path parameter is already documented as a res:// path. The description adds that the target must be a GDScript file, but gives no extra detail about path handling or invalid paths.

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: analyze a GDScript file. It also names concrete outputs (cyclomatic complexity, function count, line count), though it does not explicitly distinguish itself from siblings such as analyze_scene_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?

There is no explicit guidance on when to use this tool versus analyze_scene_complexity or analyze_signal_flow. The input type implies the context, but no when-to-use or when-not-to-use conditions are stated.

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