Skip to main content
Glama

ai_modeling_project_edit

Save 3D project metadata edits such as renames, transforms, materials, and visibility as a recoverable task tied to an expected model version, using request_id deduplication for safe retries.

Instructions

save project metadata as a recoverable task against the expected model version. Uses your Studio account and a stable request_id. Reuse returns the original job; changed input conflicts; outcome_unknown must never be blindly retried.

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": {
      "request_id": "<request_id>",
      "max_estimated_credits": "<max_estimated_credits>",
      "parameters": "<parameters>"
    },
    "name": "ai_modeling_project_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.7/5.0
Behavior4/5

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

With annotations only declaring that the tool is non-read-only, non-destructive, and open-world, the description adds real value: idempotency via a stable request_id, the conflict behavior when input changes, the existence of an outcome_unknown state, and that the task is recoverable. It still omits what the edit actually mutates; the schema shows deletions and visibility changes, but max_estimated_credits as a credit ceiling is not explained.

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?

It is three short sentences with the purpose front-loaded followed by retry constraints. Every clause carries information, and there is no redundant restatement of the name or annotations.

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

Completeness3/5

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

This is a complex mutation with nested objects and no output schema, and the description covers only the task and idempotency envelope. It does not say what classes of metadata are changed (deletions, renames, transforms, visibility) or what a successful response looks like beyond the job/conflict/outcome_unknown framing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Top-level schema description coverage is 0%, so the description must compensate. It explains request_id semantics thoroughly (stability and reuse), but says nothing about max_estimated_credits, expected_operator_id, or the parameters object itself. The nested schema documents several subfields, which supports a baseline of 3 rather than a lower score.

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 and resource: "save project metadata as a recoverable task against the expected model version." That is clearly distinct from sibling tools like ai_modeling_project_metadata (a read) or ai_modeling_project_rename (a narrower edit). It does not name those siblings explicitly, which keeps it short of a 5.

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

Usage Guidelines3/5

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

The description gives strong operational guidance on retry behavior: reusing request_id returns the original job; changed input conflicts, and an outcome_unknown result must never be blindly retried. However, it gives no guidance on when to choose this tool over ai_modeling_local_edit, ai_modeling_canvas_graph_edit, or other edit tools, so the selection decision is left implicit.

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