AI3D Studio

Convert, compress or repair a Library model

convert_model

Idempotent

Convert one of the account’s Library 3D models (a GLB) to GLB, STL, 3MF, OBJ or PLY on the server, optionally simplifying it, compressing its geometry, scaling it to a real-world size, moving its origin or repairing it for printing (holes, flipped faces, debris; STL, 3MF, OBJ or PLY), and file the result in the Library as a new creation made from it. Free (no credits) and answered at once. STL and 3MF are millimetres and Z-up for slicers; OBJ and PLY are geometry only, in metres; GLB keeps materials and textures and can be meshopt-compressed. Take asset_id from get_job or search_library (a file of a finished 3D job). Models over 50 MB or 2,000,000 triangles, and Draco-compressed GLBs, are refused. The same conversion run twice returns the same creation.

Input Schema

Name	Required	Description
`name`	No
`format`	No	The file to make; glb when omitted.
`origin`	No	Move the origin to the bottom centre (default when resizing) or the centre.
`repair`	No	Repair for printing first: weld, drop broken and duplicate faces and loose debris, fix flipped faces, fill holes. stl, 3mf, obj, ply only; up to 200,000 triangles (simplify first for more).
`asset_id`	Yes	A GLB file of one of your Library models.
`simplify`	No	Share of triangles to keep: 1 (default), 0.75, 0.5 or 0.25.
`project_id`	No
`compression`	No	GLB only: meshopt (default, smallest) or none.
`resize_height`	No	Scale the model to this height, in metres.
`resize_longest_side`	No	Scale the model so its longest side is this long, in metres. Not with resize_height.

Output Schema

Name	Required	Description
`url`	Yes	Public https download URL of the file.
`format`	Yes
`job_id`	Yes	The new Library creation: pass to get_job like any job.
`repair`	No	What repair found and fixed, when repair was asked for.
`created`	Yes	False when the same conversion was already in the Library: that creation is returned.
`asset_id`	Yes	Its file, for another convert_model.
`size_bytes`	Yes
`content_type`	Yes
`triangles_after`	Yes
`triangles_before`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: states it is free/creditless, answered synchronously, non-destructive (files the result as a NEW creation made from the source), and reinforces idempotency with 'the same conversion run twice returns the same creation'. Format-specific behaviors (units, axis orientation, material retention) and the 200k-triangle repair ceiling are disclosed.

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?

Front-loads the core capability and keeps every clause informative (formats, limits, idempotency, unit conventions). It is a dense single block rather than scannable structure, which slightly hurts readability but nothing is 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 a 10-parameter conversion tool with an output schema present, the description covers inputs sources, format semantics, constraints, cost, idempotency, and destructive-vs-additive behavior. Nothing an agent needs to call it correctly is missing.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 80%, so the baseline is 3, but the description adds real semantics beyond the schema: STL/3MF are millimetres and Z-up for slicers, OBJ/PLY are geometry-only in metres, GLB keeps materials/textures and supports meshopt. It also clarifies repair applicability and the simplify-before-repair interaction.

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 verb (convert/compress/repair) and resource (Library 3D model GLB) with the full set of output formats, and names sibling routes (get_job, search_library) for the input asset. An agent can distinguish this from generate_3d or list_models without opening schemas.

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?

Explicitly tells the agent where to obtain asset_id (get_job or search_library, a finished 3D job file) and lists refusal conditions (>50 MB, >2,000,000 triangles, Draco GLBs). It does not explicitly contrast itself against siblings like generate_3d beyond naming input sources, so it falls short of full when/when-not routing.

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

All AI3D Studio 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.

Resources

Need Help?