Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

model_details

Read-only

Retrieve full metadata for a Thingiverse model by numeric ID to view its description, instructions, license, tags, and file count.

Instructions

Get full details for a Thingiverse model.

        Args:
            thing_id: Numeric thing ID (from ``search_models`` results).

        Returns comprehensive metadata including description, instructions,
        license, tags, and file count.

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_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
thing_idYesNumeric thing ID (from ``search_models`` results).

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 (from ``search_models`` results)."
  2. First observedv0.1.0

TDQS

A3.7/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 the safety profile is covered. The description adds genuine value by enumerating what is returned (description, instructions, license, tags, file count), which matters because there is no output schema; it does not, however, mention rate limits or failure modes on the remote Thingiverse lookup.

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 definition is short and front-loads the purpose before the argument and return details. The docstring-style 'Args:'/'Returns:' framing is slightly verbose for a single parameter but costs little.

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 one-parameter read-only lookup with annotations and no output schema, the definition covers purpose, the ID source, and the returned fields. Only the substitution relationship with sibling tools (model_files, download_model) is left unstated.

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 coverage is 100% and the argument text in the description is a verbatim repeat of the schema's thing_id description ('Numeric thing ID (from ``search_models`` results)'), so no additional semantic detail is contributed. Baseline 3 applies when the schema already documents all parameters.

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 uses a specific verb and resource ('Get full details for a Thingiverse model') and implies the retrieval scope with 'full details' and the enumerated metadata fields. It does not explicitly differentiate itself from nearby siblings such as model_files or download_model, which keeps it from a 5.

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?

Usage is only implied: the model is that you have a thing_id and want its metadata. The parenthetical '(from search_models results)' helpfully signals where the ID comes from, but there is no statement of when to prefer model_details over model_files, download_model, or browse_models.

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