Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_designs

Read-only

Lists saved 3D designs with IDs, names, branches, and last-updated timestamps. Use filters and pagination to browse active or archived designs.

Instructions

List every design the user has saved — id, name, branches, last-updated.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (default 24). Hard cap applied after filtering. Default: 24.
filterNo``"all"`` (default — every non-archived design) or ``"archived"`` (only archived). ``"mine"`` and ``"shared"`` are accepted and list the same designs as ``"all"``. Default: "all".
offsetNoPagination cursor (0-based). Pass ``next_offset`` from a prior call to continue. Default: 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / filter / description
      Previous value: -"Default: \"all\"."New value: +"``\"all\"`` (default — every non-archived design) or ``\"archived\"`` (only archived).  ``\"mine\"`` and ``\"shared\"`` are accepted and list the same designs as ``\"all\"``. Default: \"all\"."
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 24."New value: +"Page size (default 24).  Hard cap applied after filtering. Default: 24."
    • changedInput schema / properties / offset / description
      Previous value: -"Default: 0."New value: +"Pagination cursor (0-based).  Pass ``next_offset`` from a prior call to continue. Default: 0."
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare a safe, read-only, closed-world operation, so the description need not repeat the safety profile. It adds value by naming the returned fields (id, name, branches, last-updated) in the absence of an output schema, but omits pagination behavior and the fact that archived designs are excluded by default — which mildly conflicts with "every design".

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?

A single front-loaded sentence with the returned fields placed after the em dash; there is no filler or redundancy.

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

Completeness3/5

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

For a simple read-only list tool the description is close to adequate, and it usefully previews the return shape since no output schema exists. It is still incomplete: it says "every design" while the default filter omits archived designs, and it says nothing about pagination flow despite offset/limit parameters.

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 the schema documents limit, filter values, and offset cursoring in detail. The description contributes nothing about parameters, so the baseline 3 for fully documented schemas applies.

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 ("List") and resource ("every design the user has saved") and even names the returned fields, so an agent knows it is an enumeration tool rather than a lookup. It stops short of naming siblings such as list_public_designs, list_cached_designs, or list_design_versions, which would be needed for 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?

The phrase "the user has saved" implicitly scopes the call to the caller's own designs, distinguishing it in spirit from public or cached listings. However, it never states when to prefer this over the many sibling list tools, nor does it mention the default archived exclusion, so usage must be inferred.

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