Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_public_designs

Read-only

List a person's public 3D designs from their Kiln profile by username, enabling you to browse or reference shared models.

Instructions

List a person's public designs, from their page at kiln3d.com/@username.

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": {
      "username": "<username>"
    },
    "name": "list_public_designs"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesThe person's username: the part of the profile address after ``@``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the agent knows this is a safe, non-destructive, closed-world read operation. The description adds that the designs are public and sourced from the person's profile page, but it does not mention pagination, authentication requirements, or what happens for missing users.

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?

The description is a single, front-loaded sentence with no wasted words. It immediately conveys the resource, scope, and source of the data.

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, read-only tool with one fully documented parameter and clear safety annotations, the description provides enough context to invoke it correctly. It does not describe the return shape or pagination behavior, but the absence of an output schema makes that omission minor rather than disqualifying.

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 already explains that username is the part of the profile address after '@'. The description provides a concrete URL example, kiln3d.com/@username, which slightly reinforces the parameter format but does not add substantial semantic 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 a person's public designs, scoped to their kiln3d.com/@username page. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as search_public_designs or get_public_design.

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 description implies the tool should be used when you know a username and want that person's public designs from their profile page. It does not provide explicit when-to-use versus when-not-to-use guidance, nor does it name an alternative tool for related tasks like searching public designs.

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