Skip to main content
Glama

godot_motion_inspect

Samples a named GLB animation at specified normalized times and saves engine-evaluated transforms for inspection.

Instructions

Sample a named GLB animation and save engine-evaluated transforms.

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>",
      "player": "<player>",
      "animation": "<animation>",
      "normalized_times": "<normalized_times>"
    },
    "name": "godot_motion_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
playerYes
sourceYes
animationYes
directoryYes
normalized_timesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and the description is consistent with that by saying it "saves" transforms. It adds one valuable behavioral detail — the transforms are engine-evaluated rather than raw file data — but says nothing about where the save lands, whether existing files are overwritten, or what idempotency means here, which matters given readOnlyHint=false.

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 or redundancy. It is efficient, though its brevity borders on under-specification given five undocumented required parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. However, this is a non-read-only tool with five 0%-documented required parameters and no indication of the write target, overwrite behavior, or preconditions — meaningfully short of what an agent needs to call it correctly.

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?

Schema description coverage is 0% across 5 required parameters, so the description must carry the burden and largely does not. It hints that "animation" names a GLB animation, but "player", "directory", "source", and the 2–9 bounded [0,1] float array "normalized_times" are entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Sample a named GLB animation and save engine-evaluated transforms" gives a verb pair (sample/save) and a resource (GLB animation), which is more than a tautology. But it never clarifies what the distinct roles of "source", "directory", and especially "player" are, so an agent cannot fully picture the operation from the description alone.

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 guidance, no prerequisites (e.g. must a Godot editor/player process already be running?), and no comparison to sibling inspect tools. The agent must infer context from the name and schema only.

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