Skip to main content
Glama

ai_modeling_uv_commit

Applies a generated UV candidate to a 3D model after verifying the current version and request ID, preventing conflicts from stale input or unsafe retries.

Instructions

apply a generated UV candidate after checking the current 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_uv_commit"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already identify this as a non-read-only, open-world, non-destructive operation. The description adds important semantics beyond that: it uses the Studio account, relies on a stable request_id, returns the original job on reuse, conflicts on changed input, and warns against blind retries after outcome_unknown.

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 definition is three dense sentences with no wasted wording. Purpose, account context, idempotency behavior, and retry safety are front-loaded and easy to scan.

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 mutating tool with a nested parameter object, no schema descriptions, and no output schema. The description covers critical operational behavior well, but it leaves key inputs such as the credit cap and the operator IDs unexplained, so it is not fully complete.

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 carry parameter meaning. It clarifies the idempotency role of request_id, but it does not explain max_estimated_credits, project_id, current_operator_id, or candidate_operator_id, leaving most nested parameters undocumented.

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 gives a specific verb and resource: "apply a generated UV candidate" after checking the current model version. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling ai_modeling_uv_apply tool, which could cause ambiguity.

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 phrase "after checking the current model version" implies a prerequisite, and the retry guidance for request_id reuse, conflicting input, and outcome_unknown gives useful operational context. However, it does not explicitly say when to use this tool versus alternatives such as ai_modeling_uv_preview or ai_modeling_uv_apply.

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