Skip to main content
Glama

Review a 3D model

godot_model_lint
Read-onlyIdempotent

Score .glb or .gltf models without Godot to catch flipped faces, open edges, missing normals, UVs or tangents, texture and naming issues, and triangle budgets.

Instructions

Score a .glb or .gltf without Godot: flipped faces, open edges, missing normals, UVs or tangents, textures, node names, budgets. Pass archetype (a name such as 'car' or 'helikopter', or an id) to also check it is what it should be: required parts, pivots, wheel axes, size (unit mistakes), direction. Pass contract to hold it to a model.contract.json, and max_triangles to flag a heavy model. Returns an overall score, a score per category (geometry, materials, performance, rig, and archetype when given) and the findings: detail brief shows up to 25 errors and warnings, full shows every finding with its fix. An error result when there are errors. Read-only. godot_model_build already lints what it builds; to see the shape use godot_model_view, for the raw contents godot_model_inspect.

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": {
      "file": "<file>"
    },
    "name": "godot_model_lint"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesPath to a .glb or .gltf file, inside the project.
detailNobrief (capped lists) or full (everything); default full
contractNoa model.contract.json inside the project
archetypeNowhat the model should be, e.g. car, helikopter, vehicle.wheeled.car
max_trianglesNoflag a model with more triangles than this

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / detail / description
      Previous value: -"brief: short output with capped lists; full: everything (default for this premium profile: full)."New value: +"brief (capped lists) or full (everything); default full"
  2. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / detail / description
      Previous value: -"Output detail (default for this premium profile: full)."New value: +"brief: short output with capped lists; full: everything (default for this premium profile: full)."
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only/idempotent/non-destructive, yet the description still adds real value: it discloses the return shape (overall score, per-category scores for geometry, materials, performance, rig and archetype), the brief cap of 25 findings versus full-with-fixes, and the notable behavior that it returns an error result when errors exist. It never contradicts the annotations, though it does not describe score ranges or runtime cost on large models.

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?

Front-loaded with the verb and the check list, then optional parameters, then return values, then sibling routing — a sensible order. It is dense and clause-heavy in one paragraph, and 'without Godot' is slightly ambiguous, but no sentence is filler.

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

Completeness5/5

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

There is no output schema, so the description must carry return semantics — and it does, covering score categories, finding detail levels, and error-result behavior. Combined with explicit sibling routing and optional-parameter effects, an agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds effect-level meaning the schema does not: archetype accepts a name like 'car'/'helikopter' or an id and triggers required-part, pivot, wheel-axis, unit-size and direction checks; contract ties it to a model.contract.json; max_triangles flags a heavy model. Only the file path and enum details are left entirely to the schema.

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

Purpose5/5

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

States a specific verb and resource ('Score a .glb or .gltf') and enumerates exactly what is checked: flipped faces, open edges, missing normals/UVs/tangents, textures, node names, budgets. It also distinguishes itself from the three model siblings by name, so an agent can pick it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing is provided: use godot_model_build when you are building (it lints its own output), godot_model_view to see the shape, godot_model_inspect for raw contents. It also explains when to escalate with optional parameters (archetype for conformance checks, contract to hold to a model.contract.json, max_triangles for weight budgets).

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