Skip to main content
Glama

ai_modeling_texture_generate

Generate model textures, PBR maps, or upscaled high-resolution textures for Studio 3D projects; use a stable request ID to reuse jobs and prevent duplicate requests.

Instructions

generate model textures, PBR maps or higher-resolution textures. 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_texture_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description discloses that it consumes a Studio account and defines idempotency behavior for request_id reuse and input changes. It does not mention credit consumption despite max_estimated_credits being required, nor how results are retrieved later.

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

Conciseness4/5

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

Three sentences, front-loaded with purpose and free of filler. The final clause ('outcome_unknown must never be blindly retried') is telegraphic and relies on a term never defined here, which costs a bit of clarity.

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

Completeness5/5

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

For a three-parameter tool with a rich nested schema and no output schema, the description covers mode selection, account context, and idempotent-retry policy. The remaining gaps, credit cost and result retrieval, would be nice but are secondary to correct invocation.

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 coverage is 0%, so the description must carry meaning; it explains request_id reuse semantics well, which is the most important parameter. It says nothing about max_estimated_credits or the parameters object beyond the mode list, though the nested schema itself supplies enum and field descriptions for most inner fields.

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 and enumerates the three modes it covers ('model textures, PBR maps or higher-resolution textures'), which maps to the action enum (generate/pbr/upscale). The resource is distinguishable from siblings like image_generate or model_generate, though no sibling is named explicitly.

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?

Provides strong guidance on retry/reuse semantics ('Reuse returns the original job; changed input conflicts; outcome_unknown must never be blindly retried'), which is genuine when-to-use context for repeats. However, it gives no selection guidance against alternatives such as image generation or canvas texture reference, leaving the choice to be inferred from the tool name.

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