Skip to main content
Glama

godot_review_prepare

Prepare a textured GLB for review as a Godot Web scene, with optional animation pose and view selection, so you can inspect the model and capture a source-bound image.

Instructions

Prepare a GLB review, optionally at a selected animation pose.

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_review_prepare"
  }
}

Input Schema

NameRequiredDescriptionDefault
poseNo
viewNothree-quarter
sourceYes
directoryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / pose
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "animation": {
      +      "maxLength": 512,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "player": {
      +      "maxLength": 512,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "time_seconds": {
      +      "minimum": 0,
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "player",
      +    "animation",
      +    "time_seconds"
      +  ],
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
  2. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the agent knows this mutates state, yet the description never says what is created or written. Since the schema has a required "directory" parameter, it presumably emits artifacts on disk, but overwrite behavior, failure modes, and side effects are undisclosed.

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. Its brevity is efficient structurally, though the terseness is better penalized under completeness than conciseness.

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?

Four parameters at 0% coverage plus a write-ish annotation profile demand more than one sentence; the presence of an output schema excuses the description from explaining return values, but nothing else is adequately covered. An agent could not reliably construct a correct call from this text alone.

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%, so the description must compensate, and it only touches one of four parameters ("pose"). It never explains what "source" points to, what "directory" receives, or what "view" (front/three-quarter/side) affects, even though the nested pose object carries three required subfields.

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?

"Prepare a GLB review" gives a verb plus a resource and hints at the artifact type (GLB), but "prepare" is opaque — it is unclear whether this writes files, generates thumbnails, or stages state. It does not distinguish itself from siblings like godot_review_capture or godot_review_inspect beyond the shared prefix.

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 only usage signal is "optionally at a selected animation pose," which implies when the pose parameter applies but not when to call this tool versus godot_review_capture, godot_review_inspect, or godot_motion_inspect. No prerequisites, ordering, or exclusions are stated.

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