Ludo AI Game Assets

create3DModel

Convert a single source image into a textured 3D model (image-to-3D). The job result is a downloadable GLB model_url plus an array of snapshot image URLs rendered from different angles (handy for previews). Accepts optional mesh controls: target_num_faces (max triangle count, 1000-200000, default 50000), texture_size (1024 or 2048, default 2048), and texture_type ("pbr", "simple", or "none", default "pbr"). Credits are held when the job is accepted and refunded if it fails or is cancelled. Pass an optional request_id to tag the result so you can locate it later via listGenerations (type 3d). Async generation job: returns {id, status} - poll getApiJob (job and credit contract: see the server instructions).

Credits: This endpoint consumes 3 credits per call.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`requestBody`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedInput schema / properties / requestBody / properties / request_id / description

Previous value: -"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable with the results endpoint."New value: +"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable as the request_id filter of listGenerations."

Changed1 schema field changedSep 17, 2026
- changedInput schema / properties / requestBody / properties / texture_size / example
```
Previous value: -1024New value: +2048
```
Changed6 schema fields changedSep 3, 2026
- removedInput schema / properties / requestBody / properties / target_num_faces / default
```
Removed value: -50000
```
- changedInput schema / properties / requestBody / properties / target_num_faces / description
```
Previous value: -"Maximum triangle count for the mesh (1000-200000)"New value: +"Maximum triangle count for the mesh (1000-200000) Default: 50000."
```
- removedInput schema / properties / requestBody / properties / texture_size / default
```
Removed value: -2048
```
- changedInput schema / properties / requestBody / properties / texture_size / description
```
Previous value: -"Texture resolution in pixels Accepted values: 1024, 2048."New value: +"Texture resolution in pixels Accepted values: 1024, 2048. Default: 2048."
```
- removedInput schema / properties / requestBody / properties / texture_type / default
```
Removed value: -"pbr"
```
- changedInput schema / properties / requestBody / properties / texture_type / description
```
Previous value: -"Texture type"New value: +"Texture type Default: \"pbr\"."
```

Changed1 schema field changedAug 30, 2026

changedInput schema / properties / requestBody / properties / request_id / description

Previous value: -"Optional client-provided identifier for this request. Use this to retrieve results later via the results endpoint."New value: +"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable with the results endpoint."

Changed4 schema fields changedApr 10, 2026

removedInput schema / properties / requestBody / properties / high_detail_shape

Removed value: -{
-  "default": false,
-  "description": "Enable higher detail shape generation. Generation time will increase and the effect is only noticeable with a high target_num_faces value (around >30.000)",
-  "example": false,
-  "type": "boolean"
-}

changedInput schema / properties / requestBody / properties / target_num_faces / description

Previous value: -"Maximum triangle count for the mesh (1000-100000)"New value: +"Maximum triangle count for the mesh (1000-200000)"

changedInput schema / properties / requestBody / properties / target_num_faces / maximum
```
Previous value: -100000New value: +200000
```

changedInput schema / properties / requestBody / properties / texture_size / description

Previous value: -"Texture resolution in pixels Accepted values: 1024, 2048, 4096."New value: +"Texture resolution in pixels Accepted values: 1024, 2048."

Changed2 schema fields changedMar 4, 2026
- changedInput schema / properties / requestBody / properties / texture_size / description
```
Previous value: -"Texture resolution in pixels"New value: +"Texture resolution in pixels Accepted values: 1024, 2048, 4096."
```
- removedInput schema / properties / requestBody / properties / texture_size / enum
```
Removed value: -[
-  1024,
-  2048,
-  4096
-]
```

Changed1 schema field changedMar 3, 2026

addedInput schema / properties / requestBody / properties / request_id

Added value: +{
+  "description": "Optional client-provided identifier for this request. Use this to retrieve results later via the results endpoint.",
+  "type": "string"
+}

AddedFeb 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses async execution, the initial `{id, status}` response, polling via getApiJob, credit holding/refunding behavior, the 3-credit cost, and the downloadable result format.

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 description is compact and front-loaded with the core purpose and result, then optional controls, credit implications, and response flow. Every sentence adds operational value, and no space is wasted on filler.

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 an async generation tool with no output schema and no annotations, this description is unusually complete. It covers inputs, options, outputs, credit semantics, result discoverability, and the polling contract, leaving an agent well equipped to invoke and monitor the job correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 compensate, and it does. It explains each meaningful parameter: image source, target_num_faces with range and default, texture_size with accepted values, texture_type enum options, and request_id behavior including deduplication and listGenerations filtering.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific, actionable purpose: 'Convert a single source image into a textured 3D model (image-to-3D)'. It names the output artifact (GLB plus preview snapshots) and is clearly distinguishable from sibling tools like animate3DModel, rigModel, and createImage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the intended use case explicit: converting a single source image to a 3D model. It does not list alternative tools or exclusions, but the context is clear enough that an agent can decide when this tool is appropriate versus the 3D animation or rigging siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ludo AI Game Assets tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

create3DModel

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources