Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

decoration_history

Read-only

Retrieve every saved version of a decoration to see when each was made, what changed, which materials it printed well on, and its print count.

Instructions

Get every version of a saved decoration (Kiln Pro).

        Each version with when it was made, what changed, the materials
        it has printed well on and its print count.

        :param name: Decoration name or slug.
        :returns: Dict with the version history and the current version.

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

Input Schema

NameRequiredDescriptionDefault
nameYesDecoration name or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / name / description
      Added value: +"Decoration name or slug."
  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 (readOnlyHint, destructiveHint=false, openWorldHint=false) already carry the safety profile, so the description's added value is the note that each version reports its timestamp, changes, materials it printed well on, and print count, plus a '(Kiln Pro)' gating hint. That is genuine extra context, but it omits ordering (newest first?), volume/pagination, and whether deleted/older versions are included.

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?

The core capability is front-loaded in the first sentence, followed by useful return-content detail. The Sphinx-style ':param'/':returns' notation is somewhat redundant against the schema, but it costs little and the whole entry stays short.

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?

With no output schema, the description does the right thing by enumerating what each version record contains and noting the current version is returned alongside the history. Remaining gaps (ordering, scope of history) are minor for a one-parameter read-only tool.

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 single `name` parameter is documented at 100% schema coverage, and the description's ':param name: Decoration name or slug' simply repeats the schema text verbatim. No additional meaning (format, ambiguity handling between name and slug) is contributed.

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: 'Get every version of a saved decoration,' with the version-history scope made explicit. That distinguishes it in spirit from decoration_info and list_decorations, though it never names those siblings directly.

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 — an agent can infer you call this when you need the full version trail rather than the current decoration metadata. There is no explicit when-to-use or when-not-to-use statement, and no routing to decoration_info or list_decorations for the adjacent questions.

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