Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_face_emboss_depth

Read-only

Returns the recommended maximum emboss or deboss depth for a given face and product type, helping you set valid decoration depths.

Instructions

Return the recommended maximum emboss/deboss depth for a face.

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>",
      "face_name": "<face_name>"
    },
    "name": "get_face_emboss_depth"
  }
}

Input Schema

NameRequiredDescriptionDefault
face_nameYesThe face's registry name (``"exterior_bottom"``) as ``list_decoratable_faces`` lists it, or the sketch's own face name for a sketch-built design. An unknown face answers ``UNKNOWN_FACE``.
product_typeYesThe product generator's type (``"jewelry_tray"``), or a sketch-built design's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / face_name / description
      Added value: +"The face's registry name (``\"exterior_bottom\"``) as ``list_decoratable_faces`` lists it, or the sketch's own face name for a sketch-built design.  An unknown face answers ``UNKNOWN_FACE``."
    • addedInput schema / properties / product_type / description
      Added value: +"The product generator's type (``\"jewelry_tray\"``), or a sketch-built design's id."
  2. Addedv1.5.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only that the result is a 'recommended maximum' depth, which is advisory context. It omits units, whether the recommendation depends on product_type geometry or material, and how unknown faces are reported (the schema handles UNKNOWN_FACE).

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 no filler or redundancy. Every word contributes to identifying the returned value.

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 two-parameter, read-only lookup with full schema coverage and annotations, the description is largely adequate. However, it omits the units of the returned depth and what the recommendation depends on, which an agent needs to use the value correctly when applying decoration.

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 both face_name and product_type are documented in the schema, including the UNKNOWN_FACE behavior and references to list_decoratable_faces. The description adds no additional meaning about these parameters, so the baseline of 3 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?

States a specific verb and resource: 'Return the recommended maximum emboss/deboss depth for a face.' An agent can tell it produces a depth recommendation for a named face. It does not name or contrast any sibling (e.g., describe_face, list_decoratable_faces), so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance, no prerequisites, and no alternatives. It never says to call this before apply_decoration/decorate_surface, nor when a caller might prefer describe_face or recommend_text_size. Usage is inferable only from the tool name and purpose.

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