Skip to main content
Glama

ai_modeling_make

Generate a 3D asset from text, an image path, a model file, or an existing task id, then block until completion and download artifacts with returned local file paths.

Instructions

Generate a 3D asset from text, an image path, a model file path, or an existing task id. Blocks until finished; downloads artifacts locally and returns file paths. Uses your Studio web credits.

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": {
      "input": "<input>"
    },
    "name": "ai_modeling_make"
  }
}

Input Schema

NameRequiredDescriptionDefault
pbrNo
thenNo
inputYes
modelNo
no_waitNo
timeoutNo
scenarioNo
output_dirNo
request_idNo
no_downloadNo

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?

Beyond the annotations (readOnly=false, openWorld=true, destructive=false), the description adds meaningful behavior: it blocks until finished, downloads artifacts to local disk and returns file paths, and consumes Studio web credits. That is real context an agent cannot get from the structured fields. It omits auth requirements and the maximum blocking time (7200s), keeping it off 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 short sentences, front-loaded with what the tool produces and its input modes, then the blocking/download behavior, then cost. No filler and no repetition of 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 complex, long-running, credit-consuming generation tool with no output schema, the description gives the essential output shape (local file paths) and cost signal, but leaves the majority of the ten parameters unexplained and does not describe failure or timeout behavior. Adequate to get a call started, not enough to use the optional controls correctly.

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 coverage is 0% across 10 parameters, so the description must carry the load and only partially does: it explains the input modes that map to 'input' and 'model', but says nothing about pbr, then, scenario, output_dir, no_download, timeout, no_wait, or request_id. Six-plus parameters remain wholly undocumented, which is a significant gap for a 10-param tool.

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?

Uses a specific verb ('Generate') and resource ('3D asset') and enumerates the four accepted input modes (text, image path, model file path, existing task id), which is more than a restatement of the name. It does not explicitly differentiate itself from any sibling, so it stops short of the top mark, but the purpose is unambiguous.

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 implies usage ('generate a 3D asset') and discloses that the call blocks until completion plus a credit cost, which helps an agent decide whether to invoke it. However, it never states when to prefer this over alternatives or how the blocking default interacts with the no_wait/timeout parameters present in the schema, leaving the caller to infer.

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