Skip to main content
Glama

ai_modeling_project_metadata

Edits 3D project part transforms, names, visibility, and material factors against an expected model version to prevent conflicting updates.

Instructions

Edit part transforms, names, visibility and material factors against an expected model version.

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": {
      "project_id": "<project_id>",
      "expected_operator_id": "<expected_operator_id>"
    },
    "name": "ai_modeling_project_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
replaceNoRestore supplied maps as a complete edit snapshot, including empty maps.
project_idYes
children_renameNo
material_factorNo
children_deletedNo
expected_metadataNoPreviously read metadata for a local conflict check; upstream has no atomic compare-and-swap.
children_visibilityNoOriginal mesh name → visible; false deletes, true restores without replacing unrelated selections.
expected_operator_idYes
children_transform_matrixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds useful behavioral context by saying the edit is checked against an expected model version, which signals optimistic concurrency. However, it does not disclose what gets destroyed or replaced, does not mention that visibility=false can delete meshes, and does not explain snapshot semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single tightly written sentence with the edit scope and concurrency condition front-loaded. There is no filler or repetition, so every word earns its place.

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?

This is a 9-parameter nested mutation tool with no output schema and low schema description coverage. The one-sentence description is too thin for that complexity: it omits replace behavior, deletion semantics, the expected_metadata conflict check, and required identifier handling. An agent could call it, but without enough context to avoid misuse.

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 only 33%, so the description must compensate for undocumented parameters. It lists the edited attribute groups (transforms, names, visibility, material factors), which partially maps to the schema, but it does not explain project_id, expected_operator_id, expected_metadata, replace, or children_deleted semantics. Coverage is therefore still substantially missing.

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 uses a specific verb ('Edit') and names the editable resource attributes: transforms, names, visibility, and material factors. It also adds the concurrency condition 'against an expected model version,' making the operation distinguishable as a metadata edit. However, it does not explicitly distinguish itself from related siblings such as ai_modeling_model_metadata_apply or ai_modeling_project_edit.

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 phrase 'against an expected model version' implies that a prior read is needed, but the description does not state when to use this tool versus alternatives. It names no sibling and gives no exclusions or prerequisites, leaving the agent to infer the workflow.

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