Skip to main content
Glama

ai_modeling_model_metadata_apply

Applies Studio part transformations, visibility, names, deletions, and PBR factors to an original GLB locally while preserving materials and coordinates.

Instructions

Apply Studio part transforms, visibility, names and PBR factors to the original GLB locally; keep materials and coordinates.

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": {
      "model_path": "<model_path>",
      "source_metadata": "<source_metadata>",
      "destination_path": "<destination_path>"
    },
    "name": "ai_modeling_model_metadata_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_pathYes
source_metadataYes
destination_pathYes
expected_source_sha256No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description usefully adds that processing happens locally and that materials and coordinates are preserved. It does not disclose what happens to an existing file at destination_path, how children_deleted relates to the non-destructive hint, or the role of the sha256 integrity check.

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?

One front-loaded sentence with no filler, and the preservation clause is placed where it matters most. It is dense but readable; nothing is wasted.

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?

A file-writing mutation over a nested metadata object with no output schema and no documented return value, overwrite behavior, or failure mode. For a tool that transforms a GLB on disk, the description leaves too much of the operational contract unstated.

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?

With 0% schema description coverage, the description must carry parameter meaning, and it only partially does: 'transforms, visibility, names, PBR factors' loosely maps to children_transform_matrix, children_deleted, children_rename and material_factor. The three required path/integrity parameters (model_path, destination_path, expected_source_sha256) get no explanation at all.

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?

A specific verb ('Apply') with a concrete list of what is applied (part transforms, visibility, names, PBR factors) to a named resource ('the original GLB'). It is clearly distinct from file-generation or retexture siblings, though it never names an alternative to route against.

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 says what happens but not when to choose this over ai_modeling_project_metadata, ai_modeling_retexture_apply, or ai_modeling_uv_apply, nor what prerequisites exist (e.g. a prior inspect/metadata read). Usage is only inferable from the verb.

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