Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

model_files

Read-only

List downloadable files for a Thingiverse model by thing ID, returning each file's name, size, and download URL so you can choose a file_id for download_model.

Instructions

List downloadable files for a Thingiverse model.

        Args:
            thing_id: Numeric thing ID.

        Returns a list of files with name, size, and download URL.
        Use ``download_model`` with the ``file_id`` to save a file locally.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "thing_id": "<thing_id>"
    },
    "name": "model_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
thing_idYesNumeric thing ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / thing_id / description
      Added value: +"Numeric thing ID."
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety and network exposure are covered. The description adds value beyond that by stating the return contents (name, size, download URL), which lets the agent know it can inspect file sizes before downloading.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and download_model pointer are front-loaded and useful, but the docstring-style 'Args' section duplicates the schema field description word for word and earns no place. Trimming it would leave a tighter, equally complete definition.

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?

With no output schema, the description correctly compensates by describing what the file list contains, and the single-parameter surface is fully covered. A note on whether the listing can be empty or requires the model to be published would close the remaining gap.

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% and there is a single required parameter, so the schema already fully documents thing_id. The description's 'Args' block merely restates 'Numeric thing ID' verbatim, adding no format, range, or provenance detail beyond the schema.

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

Purpose4/5

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

The description states a specific verb and resource ('List downloadable files for a Thingiverse model') and scopes it to the Thingiverse model domain, which separates it from printer-local siblings like printer_files. It doesn't explicitly contrast with other listing tools such as list_cached_models, so it stops short of full sibling differentiation.

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?

It gives clear forward guidance: use download_model with the returned file_id to save a file locally, which tells the agent this is the discovery step in a two-call workflow. It offers no explicit when-not-to-use guidance or exclusions, but the intended place in the flow is unambiguous.

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

Deploy Server

Other Tools