Skip to main content
Glama

ai_modeling_retexture

Generate a Magic Brush retexture preview from a camera-aligned snapshot using your Studio account and a stable request_id; reuse fetches the original job, while changed inputs conflict.

Instructions

generate a Magic Brush image preview from a camera-aligned snapshot. 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"
  }
}

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 only say readOnly=false, openWorld=true, destructive=false; the description adds materially more: it requires a Studio account (auth dependency), uses request_id for idempotency, returns the original job on reuse, conflicts on changed input, and warns that an 'outcome_unknown' state must not be blindly retried. That is concrete behavioral and safety context beyond the structured hints. It stops short of describing credit spend or the returned payload, so not a 5.

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 tight sentences with the purpose front-loaded, followed by the auth/identity mechanics and then the retry hazard. No filler wording and nothing repeated from the schema 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?

For a job-submitting, credit-consuming generation tool with a nested params object and no output schema, the definition omits what comes back (job id, status, preview handle) and how to retrieve results via the sibling get/apply tools. The idempotency and retry guidance partially compensates, but an agent still cannot fully predict the call-return-followup cycle from this text.

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 carries the full burden, and it only really explains request_id (stable, reuse semantics, conflict on changed input). max_estimated_credits — a credit cap that governs a billable generation — is never mentioned, and the nested parameters object (project_id, prompt, image_path, camera_matrix 16-element layout, strength range/default, expected_operator_id) is only loosely alluded to via 'camera-aligned snapshot.'

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?

States a specific verb and resource: 'generate a Magic Brush image preview from a camera-aligned snapshot,' which tells an agent exactly what artifact is produced and from what input. It never names the companion tools (retexture_get, retexture_apply), so the boundary between 'submit job' and 'fetch/apply result' has to be inferred from sibling names alone, which keeps it below 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 real operational guidance about idempotent reuse and the conflict case, but that is retry/submission behavior rather than when-to-call-this-vs-an-alternative guidance. There is no statement such as 'call this to queue the job, then use ai_modeling_retexture_get to poll,' so an agent must guess the workflow position of this tool.

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