Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_decoration_preset

Read-only

Fetches the full record for one decoration preset by preset ID or exact version ID, so agents can inspect a specific preset version before reusing it in a 3D design.

Instructions

Fetch ONE decoration preset — the full record for a single preset or an exact version.

Needs Kiln Pro.

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": "get_decoration_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
preset_idNoId of the preset; returns its latest version. Give this or ``preset_version_id``, not both.
preset_version_idNoId of one exact preset version, including an older one. Give this or ``preset_id``, not both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / preset_id / description
      Added value: +"Id of the preset; returns its latest version.  Give this or ``preset_version_id``, not both."
    • addedInput schema / properties / preset_version_id / description
      Added value: +"Id of one exact preset version, including an older one.  Give this or ``preset_id``, not both."
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description's only additive behavioral context is the "Needs Kiln Pro" entitlement requirement, which is genuinely useful and not in the annotations; it says nothing about what the "full record" contains or how missing/wrong IDs behave.

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?

Two short sentences with the key scope constraint front-loaded and no filler. The entitlement note is terse enough to earn its place, though the em-dash clause is a little compressed.

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 read-only, two-parameter lookup with fully documented schema and no output schema, the definition covers the essentials: what is returned (full record), the two lookup modes, and the tier requirement. Only the shape of the returned record is left unspecified, which is a minor gap given no output schema exists.

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 states the mutual exclusivity of preset_id and preset_version_id. The description's phrase "a single preset or an exact version" merely restates the two schema branches rather than adding format or semantics beyond them, so the baseline 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 ("Fetch ONE decoration preset") and specifies the returned payload as "the full record for a single preset or an exact version." The emphasis on "ONE" implicitly contrasts with the sibling list_* tools, but no sibling is named 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?

Usage is only implied: "ONE" suggests this is the single-record lookup rather than a listing, and "Needs Kiln Pro" gives a gating prerequisite. It never states when to prefer preset_id vs preset_version_id at the workflow level, nor names list_decoration_presets or list_decoration_preset_versions as the alternatives.

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