Skip to main content
Glama

image_to_3d_create

Generate a 3D model from a single image by providing a publicly accessible URL or base64 data URI.

Instructions

Generate a 3D model from a single image. The image_url must be publicly accessible or a base64 data URI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
image_urlYesPublicly accessible image URL or base64 data URI
ai_modelNoAI model to use
model_typeNoModel type for generation
topologyNo'quad' or 'triangle'
target_polycountNoTarget polygon count
symmetry_modeNoSymmetry mode for the model
should_remeshNoWhether to remesh the output
should_textureNoWhether to generate textures
enable_pbrNoEnable PBR textures
texture_promptNoAdditional texture description
texture_image_urlNoReference image URL for texture
moderationNoScreen input for potentially harmful content
save_pre_remeshed_modelNoStore pre-remesh GLB model
pose_modeNoPose mode for characters
image_enhancementNoOptimize input image (default true)
remove_lightingNoRemove highlights and shadows (default true)
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention that the operation is likely asynchronous (given the 'wait_for_task' sibling) or what the return value is (task ID vs. model file), leaving significant gaps.

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?

Two sentences with no unnecessary words. The critical constraint is front-loaded, making it easy to parse.

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

Completeness2/5

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

With 16 parameters and no output schema, the description is too brief. It omits details about async behavior, error conditions, supported image types, and what the output represents, which is insufficient for a complex generative tool.

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?

Schema description coverage is 100%, so baseline is 3. The description adds the image_url constraint, but the schema already describes it similarly. No further elaboration on other parameters is provided.

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?

The description clearly states 'Generate a 3D model from a single image' with a specific verb and resource. It distinguishes from siblings like text_to_3d_create and multi_image_to_3d_create.

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?

It provides a key constraint (image_url must be publicly accessible or base64) but does not guide when to use this tool versus alternatives or specify prerequisites like supported image formats.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gwizards/meshy-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server