Skip to main content
Glama

ai_modeling_retexture_apply

Apply baked per-part Magic Brush textures to the current model using your Studio account and a stable request_id; reuse returns the original job, and outcome_unknown must not be blindly retried.

Instructions

apply baked per-part Magic Brush textures to the current model (may consume credits). 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_retexture_apply"
  }
}

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?

Adds real value beyond the annotations: credit consumption, Studio-account authentication, request_id idempotency semantics (reuse returns the original job, changed input conflicts), and the critical retry hazard for outcome_unknown. What is missing is what a successful apply does to existing model textures and what the caller gets back to track the job.

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?

Three dense sentences, front-loaded with the action and scope, then safety-relevant caveats. No filler; the parenthetical credit warning and the semicolon-delimited idempotency rules are efficiently packed.

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?

The retry/credit/auth context is strong, but for a nested-parameter, potentially credit-consuming mutation with no output schema, the definition leaves key caller questions unanswered: what max_estimated_credits governs, what the response contains, and how to retrieve the resulting job.

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% and there are three required parameters plus a nested parameters object with image_map, project_id, and expected_operator_id. The description explains only request_id semantics; max_estimated_credits (a credit safety cap), project_id, expected_operator_id, and the part_name/image_path mapping are entirely undocumented in both schema and description.

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?

Clear specific verb+resource: 'apply baked per-part Magic Brush textures to the current model'. The qualifier 'baked' and 'per-part' distinguishes it from a texture-generation call like ai_modeling_retexture, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

Implies prerequisites (textures must already be baked per part) and warns that credits may be consumed, plus a retry rule. However, it never says when to choose this over ai_modeling_retexture or how to follow up with ai_modeling_retexture_get, so selection guidance is implied rather than explicit.

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