Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_decoratable_faces

Read-only

Lists a product's decoratable faces and the matching decorate_surface face= value for each, so you can target surfaces by product type or design ID.

Instructions

List a product's decoratable faces and the decorate_surface face= value for each.

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": {
      "product_type": "<product_type>"
    },
    "name": "list_decoratable_faces"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_typeYesThe product generator's type (``"jewelry_tray"``), or a sketch-built design's id. A name that is neither answers ``UNKNOWN_PRODUCT_TYPE`` with the known product types.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / product_type / description
      Added value: +"The product generator's type (``\"jewelry_tray\"``), or a sketch-built design's id.  A name that is neither answers ``UNKNOWN_PRODUCT_TYPE`` with the known product types."
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare this as a read-only, non-destructive, closed-world operation, so the safety profile is covered. The description adds useful behavioral context by saying each result includes the decorate_surface face= value. It does not describe the face identifier format, ordering, or stability, which matters because there is no output schema.

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 that says what is listed and what downstream value is returned for each face. There is no redundant or wasted wording.

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 described parameter and no output schema, the description covers the essential return value and its link to decorate_surface. It could still say more about the face identifier format or list ordering, but nothing critical is missing for selection.

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?

The input schema has 100% description coverage for product_type, including accepted values and the UNKNOWN_PRODUCT_TYPE error behavior. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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: it lists a product's decoratable faces. It also clarifies that the output includes the decorate_surface face= value, which distinguishes it from generic face-listing tools. However, it does not explicitly distinguish itself from adjacent tools such as get_product_faces or describe_face.

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 mention of the decorate_surface face= value implies this tool is used before decorating a surface. But there is no explicit when-to-use or when-not-to-use guidance, and no named alternative is given.

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