Skip to main content
Glama

download_model

Download 3D model files from marketplaces such as Thingiverse to local storage. Select a specific file or download all files for a model.

Instructions

Download model file(s) from a marketplace to local storage.

        **Community models are unverified.** Always preview dimensions and
        validate the mesh (``validate_generated_mesh``) before printing.
        Models with high download counts and positive ratings are generally
        safer.  AI-generated or untested designs can damage delicate printer
        hardware — prefer proven blueprints when possible.

        Args:
            file_id: Numeric file ID (from ``model_files`` results).  If
                omitted and ``model_id`` is provided, downloads all files
                for the model.
            dest_dir: Local directory to save the file in (default:
                the system temp directory).
            file_name: Override the saved file name (single-file mode only).
                Defaults to the original name from the marketplace.
            model_id: Model/thing ID.  When ``file_id`` is omitted,
                all files for this model are downloaded.
            source: Marketplace source — ``"thingiverse"`` (default),
                ``"myminifactory"``, etc.
            download_all: When True, downloads all files for the model
                regardless of whether ``file_id`` is provided.

        After downloading, validate with ``validate_generated_mesh``, then
        upload to a printer with ``upload_file`` and print with ``start_print``.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNothingiverse
file_idNo
dest_dirNo
model_idNo
file_nameNo
download_allNo
Behavior3/5

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

The description warns about community models being unverified and recommends validation. It also specifies default behavior for parameters (e.g., dest_dir defaults to system temp). But it lacks details on permission requirements, disk space implications, or error handling. With no annotations, the description carries the full burden but is not exhaustive.

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?

The description is well-structured with a clear purpose statement, safety notes, and a docstring-style parameter list. While the safety warnings are important, they add some verbosity. The key information is front-loaded, making it easy to understand.

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?

Given the tool has 6 parameters, no output schema, and no annotations, the description covers the essential information: parameter details, workflow, and safety considerations. It does not discuss error conditions or edge cases, but it is sufficient for an agent to use the tool 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%, but the description provides detailed parameter semantics: it explains the relationship between file_id, model_id, and download_all, gives defaults, and describes the purpose of each parameter. This fully compensates for the missing schema descriptions.

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 the tool's purpose: 'Download model file(s) from a marketplace to local storage.' It specifies the verb (download), resource (model files), and source (marketplace). This distinguishes it from sibling tools like 'model_files' (which lists files) and 'upload_file' (which uploads).

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 provides a clear workflow after downloading: validate with validate_generated_mesh, upload with upload_file, and print with start_print. However, it does not explicitly state when to use this tool versus alternatives like 'model_files' or 'download_generated_model', nor does it mention prerequisites or when not to use it.

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/codeofaxel/kiln'

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