Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_cached_models

Read-only

Lists all 3D models in this machine's local Kiln cache, newest first, with pagination via limit and offset. Use it to see what this install has cached before printing or slicing.

Instructions

List all models in the local cache, newest first.

        Args:
            limit: Maximum results (default 50).
            offset: Number of entries to skip for pagination.

        The response declares its ``scope``: this cache is local to
        this machine, so the count is what THIS install has cached,
        not everything the user has ever downloaded or generated.
        It is also a page — ``limit``/``offset`` bound it further.

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": "list_cached_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default 50). Default: 50.
offsetNoNumber of entries to skip for pagination. Default: 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 50."New value: +"Maximum results (default 50). Default: 50."
    • changedInput schema / properties / offset / description
      Previous value: -"Default: 0."New value: +"Number of entries to skip for pagination. Default: 0."
  2. Changed4 schema fields changedv1.5.0
    • removedInput schema / properties / limit / default
      Removed value: -50
    • addedInput schema / properties / limit / description
      Added value: +"Default: 50."
    • removedInput schema / properties / offset / default
      Removed value: -0
    • addedInput schema / properties / offset / description
      Added value: +"Default: 0."
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds genuine context beyond that: the result is scoped to this machine's cache (not the user's full download history) and is further bounded by pagination, which prevents an agent from misreading counts as global.

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 leading sentence is front-loaded and useful, and the scope caveat earns its place. But the indented Args section duplicates schema content verbatim, and the phrasing 'The response declares its scope' is roundabout for a tool with no output schema to back that claim.

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 simple two-parameter, read-only listing tool with no output schema, the description covers the essentials: what is listed, ordering, pagination shape, and the locality constraint on the count. Missing only an explicit sibling comparison, which is a modest gap given the tool's simplicity.

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 limit and offset are already documented with types and defaults; the Args block largely repeats this. The additional value is minor framing ('a page — limit/offset bound it further'), consistent with the baseline of 3 when the schema does the heavy lifting.

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?

States a specific verb and resource (list models in the local cache) plus ordering ('newest first'), which is concrete enough to distinguish it from mutating siblings like cache_model or delete_cached_model. It does not explicitly differentiate itself from close siblings such as search_cached_models, get_cached_model, or list_cached_designs, so an agent must infer the boundary.

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?

'List all models in the local cache' implies the browsing use case, and the scope note hints that a call returns only what this machine holds. However, there is no explicit guidance on when to prefer this over search_cached_models or get_cached_model, and no stated preconditions or exclusions.

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