Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

detect_circular_dependencies

Detect circular script and resource dependencies in a Godot project to find reference loops that can cause build or load issues.

Instructions

Detect circular script/resource dependencies 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": "detect_circular_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and does not meet it. It never says whether the scan is read-only or has side effects, how expensive it is on large projects, whether it follows transitive dependencies or only direct ones, or what it returns; only the scope word 'in the project' adds any context beyond the name.

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 sentence, front-loaded with the verb and resource, containing no filler or repetition of the title. Nothing could be trimmed without losing the scope qualifier.

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 zero-parameter analysis tool with no output schema, the description never hints at the shape or content of the results (e.g. cycles found, paths, severity), leaving the agent unable to anticipate the return value. It is minimally adequate: the action and scope are stated, but the outcome is opaque.

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 the schema has nothing to explain and the baseline of 4 applies. The description correctly implies a project-wide scan with no filtering arguments, matching the empty input schema.

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 (Detect) and a specific resource (circular script/resource dependencies) with scope (in the project). It is clear what the tool does, but it makes no reference to the closely related sibling get_script_dependencies, so an agent must infer the boundary itself.

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 statement of when to reach for this tool versus get_script_dependencies or any analysis sibling, no prerequisites, and no exclusions. Usage is only implied by the tool name and the single clause about project scope.

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