Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

resolve_template_decoration

Read-only

Merge profile defaults with user overrides to determine effective decoration settings—face, mode, scale, depth, material, and image style—for a 3D template.

Instructions

Resolve decoration settings for a template, merging profile defaults with overrides (Pro).

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": {
      "template_id": "<template_id>"
    },
    "name": "resolve_template_decoration"
  }
}

Input Schema

NameRequiredDescriptionDefault
faceNoOverride face (empty = use profile default). Default: "".
modeNoDecoration mode override — ``emboss`` (raised) or ``deboss`` (carved in); empty uses the template profile's recommended mode. Default: "".
scaleNoOverride scale (0 = use profile default). Default: 0.0.
depth_mmNoOverride depth in mm (0 = use profile default). Default: 0.0.
materialNoMaterial for depth resolution. Default: "PLA".
image_styleNoOverride image style (empty = use profile default). Default: "".
template_idYesTemplate slug (e.g. ``"nameplate"``).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.5.1
    • changedInput schema / properties / depth_mm / description
      Previous value: -"Default: 0.0."New value: +"Override depth in mm (0 = use profile default). Default: 0.0."
    • changedInput schema / properties / face / description
      Previous value: -"Default: \"\"."New value: +"Override face (empty = use profile default). Default: \"\"."
    • changedInput schema / properties / image_style / description
      Previous value: -"Default: \"\"."New value: +"Override image style (empty = use profile default). Default: \"\"."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"PLA\"."New value: +"Material for depth resolution. Default: \"PLA\"."
    • changedInput schema / properties / mode / description
      Previous value: -"Default: \"\"."New value: +"Decoration mode override — ``emboss`` (raised) or ``deboss`` (carved in); empty uses the template profile's recommended mode. Default: \"\"."
    • changedInput schema / properties / scale / description
      Previous value: -"Default: 0.0."New value: +"Override scale (0 = use profile default). Default: 0.0."
    • addedInput schema / properties / template_id / description
      Added value: +"Template slug (e.g. ``\"nameplate\"``)."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/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 the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: the merge order (profile defaults overlaid by overrides) and that the tool is Pro-gated. It stops short of saying what 'Pro' means operationally (error vs. degraded result) or what the resolved output looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the verb out front and zero filler. It is efficient, though for a 7-parameter resolver the terseness leaves real questions unanswered, so it is lean rather than exemplary.

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?

No output schema exists, so the description should at least sketch what a 'resolved' decoration result contains; it does not. It also omits failure behavior for unknown template slugs or non-Pro accounts, which matters given the explicit Pro gate.

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 coverage is 100%, so every parameter is already documented with its sentinel/default semantics (empty string or 0 = use profile default). The description's merge clause gives context for why those sentinels exist, but adds no format, range, or constraint detail beyond the schema. Baseline 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?

States a specific verb ('resolve') and resource ('decoration settings for a template') plus the core mechanic (merging profile defaults with overrides). It is distinguishable from siblings like apply_decoration or decoration_info, though it does not name any of them explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The verb 'resolve' plus '(Pro)' implies you call it to compute effective settings before applying a decoration, but that routing is left entirely to inference across a very crowded sibling set (apply_decoration, save_decoration, decoration_info, get_face_emboss_depth).

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