Skip to main content
Glama

Convert, compress or repair a Library model

convert_model
Idempotent

Convert one of the account’s Library 3D models (a GLB, OBJ or STL file) 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. Name exactly one source: asset_id, from get_job or search_library (a file of a finished 3D job), or uploaded_file_id, the asset_id canvas_upload_commit answered for a GLB, OBJ or STL you uploaded (with board_id when it is on a Canvas Studio board, where a teammate's file that board holds may be converted too). Models over 50 MB or 2,000,000 triangles, and Draco-compressed GLBs, are refused. An OBJ is read alone, as geometry (no mtl or texture), and an STL as millimetres, Z-up. The same conversion run twice returns the same creation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "convert_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
formatNoThe file to make; glb when omitted.
originNoMove the origin to the bottom centre (default when resizing) or the centre.
repairNoRepair 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_idNoA GLB, OBJ or STL file of one of your Library models. Exactly one of asset_id and uploaded_file_id.
board_idNoThe Canvas Studio board the file is on: a teammate’s file is read only from a board that shows it and that you may run on.
simplifyNoShare of triangles to keep: 1 (default), 0.75, 0.5 or 0.25.
project_idNo
compressionNoGLB only: meshopt (default, smallest) or none.
resize_heightNoScale the model to this height, in metres.
uploaded_file_idNoA GLB, OBJ or STL file you uploaded: the `asset_id` canvas_upload_commit answered. Exactly one of asset_id and uploaded_file_id.
resize_longest_sideNoScale the model so its longest side is this long, in metres. Not with resize_height.

Output Schema

NameRequiredDescriptionDefault
urlYesPublic https download URL of the file.
formatYes
job_idYesThe new Library creation: pass to get_job like any job.
repairNoWhat repair found and fixed, when repair was asked for.
createdYesFalse when the same conversion was already in the Library: that creation is returned.
asset_idYesIts file, for another convert_model.
size_bytesYes
content_typeYes
triangles_afterYes
triangles_beforeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / asset_id / description
      Previous value: -"A GLB, OBJ or STL file of one of your Library models."New value: +"A GLB, OBJ or STL file of one of your Library models. Exactly one of asset_id and uploaded_file_id."
    • addedInput schema / properties / board_id
      Added value: +{
      +  "description": "The Canvas Studio board the file is on: a teammate’s file is read only from a board that shows it and that you may run on.",
      +  "maxLength": 191,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / uploaded_file_id
      Added value: +{
      +  "description": "A GLB, OBJ or STL file you uploaded: the `asset_id` canvas_upload_commit answered. Exactly one of asset_id and uploaded_file_id.",
      +  "maxLength": 191,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "asset_id"
      -]
  2. Changed1 schema field changed
    • changedInput schema / properties / asset_id / description
      Previous value: -"A GLB file of one of your Library models."New value: +"A GLB, OBJ or STL file of one of your Library models."
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say it is a non-destructive, idempotent, closed-world write; the description adds materially new behavior: it is free, answers synchronously, returns a new Library creation rather than mutating the source, is deterministic across repeated runs, and refuses oversized or Draco-compressed inputs. That goes well beyond the supplied hints.

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?

Dense and front-loaded on purpose, with the core conversion stated first and constraints after; almost every clause carries information. It is a single sprawling sentence chain, though, and the source-selection rule buried mid-paragraph would be easier to act on if split out.

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

Completeness4/5

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

For a 12-parameter tool with an output schema, the description covers formats, units, limits, determinism and source selection thoroughly. The gap is project_id and name, which are never mentioned even though the result is filed as a new creation in the Library, leaving the agent to infer how the output is named and placed.

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 coverage is already 83%, but the description adds cross-parameter meaning the schema cannot: the mutual exclusivity of asset_id and uploaded_file_id, the board_id permission condition, the unit/axis conventions per output format (STL/3MF millimetres Z-up, OBJ/PLY metres geometry-only, GLB with materials), and repair's 200,000-triangle ceiling. These are semantics rather than restatements.

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?

Opens with a specific verb and resource ('Convert ... Library 3D models') and enumerates the supported input and output formats, plus the optional simplify/compress/resize/origin/repair operations. It also distinguishes the tool from the asset-lookup siblings by naming get_job and search_library only as sources of asset_id.

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

Usage Guidelines5/5

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

Explicitly tells the agent to name exactly one source, where each value comes from (asset_id from get_job or search_library, uploaded_file_id from canvas_upload_commit), and when board_id is needed. It also sets the boundary conditions under which the call is refused (50 MB, 2,000,000 triangles, Draco GLBs), which is the practical when-not guidance for this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources