Skip to main content
Glama

godot_asset_inspect

Inspects a self-contained GLB asset in Godot and saves a source-bound scene report, so you can verify scene structure and contents before review.

Instructions

Inspect a self-contained GLB with Godot and save a source-bound scene report.

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": {
      "source": "<source>",
      "directory": "<directory>"
    },
    "name": "godot_asset_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
directoryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, and the description's "save a source-bound scene report" is consistent with that write side-effect, which is worth some credit. Beyond that, it discloses nothing about where the report is written, whether it overwrites existing output, whether a Godot project/editor must be running, or how long the operation takes.

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 no filler; the key action and artifact come first. Its brevity borders on under-specification rather than elegance, but nothing in it is wasted.

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?

Having an output schema means return values need not be explained, which lowers the burden. However, for a tool with two fully undocumented parameters and an opaque artifact concept ("source-bound scene report"), the description leaves an agent guessing about inputs and side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters (source, directory) have 0% schema description coverage and the description does not compensate. One can guess that "source" is the GLB path and "directory" is the report destination from "save a ... report", but neither is stated, nor is the expected path format or whether directory must exist.

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 names a specific verb ("Inspect") and resource ("self-contained GLB") plus the engine used and the output artifact (a source-bound scene report). It is clear what the tool does, but it does nothing to distinguish itself from siblings like godot_motion_inspect or godot_review_inspect, so the agent must infer which inspect variant applies.

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 when-to-use or when-not-to-use guidance, and no prerequisites are stated. The phrase "self-contained GLB" hints at an input constraint, but the description never says what to do for non-self-contained assets or how this differs from the other inspect tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.