Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_project_statistics

Retrieve high-level project statistics, including file counts by type and total scene nodes, to quickly assess project structure and size.

Instructions

Get high-level statistics about the project (file counts by type, total scene nodes, etc.).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. 'Get' implies read-only, but it does not say whether the call is expensive (scanning the filesystem/scene tree), whether results are cached, or what the response looks like, which matters for a tool with no output schema.

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?

A single front-loaded sentence with the key framing ('high-level statistics') first and clarifying examples second. Nothing is redundant, though the trailing 'etc.' leaves the scope fuzzy rather than crisp.

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?

With no output schema and no annotations, the description is the only source of information about the return value, and 'etc.' plus 'high-level' is only a partial sketch. It is adequate to know roughly what comes back but insufficient to plan around the result's structure or cost.

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; the baseline applies. The parenthetical does usefully hint at the shape of the output even though no parameter meaning is needed.

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 ('Get high-level statistics about the project') and names concrete examples of the returned data (file counts by type, total scene nodes). It is clear, though it does not distinguish itself from the nearby get_project_info or get_editor_performance beyond 'statistics'.

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 or when-not-to-use guidance, and does not mention the closely named siblings such as get_project_info that an agent could easily confuse it with. Usage must be inferred entirely from the phrase 'high-level statistics'.

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