Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

record_filament_colour

Record the actual printed colour of a filament, with brand, material, and observed hex, so Kiln’s colour suggestions reflect real print results.

Instructions

Tell Kiln what colour a filament really printed, so its colour suggestions show your result.

Needs Kiln 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": {
      "brand": "<brand>",
      "line": "<line>",
      "material": "<material>",
      "colour": "<colour>",
      "observed_hex": "<observed_hex>",
      "observed_by": "<observed_by>"
    },
    "name": "record_filament_colour"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineYesIts product line, e.g. ``"PLA Basic"``.
noteNoAnything worth keeping with it -- the light, the settings -- up to 280 characters. Default: "".
brandYesThe filament's maker, as the suggestion shows it.
colourYesIts colour name, e.g. ``"Jade White"``.
materialYesIts material, e.g. ``"PLA"``.
printer_idNoThe machine that printed it, if you want it kept. Default: "".
observed_byYes``"colorimeter"``, ``"photo"`` or ``"eye"``.
observed_hexYesThe colour the print came out, e.g. ``"#C9D3BE"``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.5.1
    • addedInput schema / properties / brand / description
      Added value: +"The filament's maker, as the suggestion shows it."
    • addedInput schema / properties / colour / description
      Added value: +"Its colour name, e.g. ``\"Jade White\"``."
    • addedInput schema / properties / line / description
      Added value: +"Its product line, e.g. ``\"PLA Basic\"``."
    • addedInput schema / properties / material / description
      Added value: +"Its material, e.g. ``\"PLA\"``."
    • changedInput schema / properties / note / description
      Previous value: -"Default: \"\"."New value: +"Anything worth keeping with it -- the light, the settings -- up to 280 characters. Default: \"\"."
    • addedInput schema / properties / observed_by / description
      Added value: +"``\"colorimeter\"``, ``\"photo\"`` or ``\"eye\"``."
    • addedInput schema / properties / observed_hex / description
      Added value: +"The colour the print came out, e.g. ``\"#C9D3BE\"``."
    • changedInput schema / properties / printer_id / description
      Previous value: -"Default: \"\"."New value: +"The machine that printed it, if you want it kept. Default: \"\"."
  2. Addedv1.5.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish this is a non-destructive write with no open-world access, so the bar is lower. The description adds real context beyond them: it requires Kiln Pro (a tier/auth gate) and the write has a downstream effect on colour suggestions. It does not disclose duplicate-handling or whether prior records are overwritten.

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?

Two short sentences, front-loaded with the action and benefit, followed by the one hard prerequisite. Nothing is wasted or buried.

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 simple non-destructive write with full schema coverage and annotations, the essentials are present. Still missing is what happens on repeat submissions for the same filament, and whether a confirmation or identifier is returned; with no output schema, that gap falls on the description.

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%, so every one of the eight parameters is already documented with examples. The description confirms the observed-versus-named colour framing but adds no syntax, format, or constraint details beyond the schema, making the baseline 3 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 and resource: record the colour a filament actually printed, feeding back into Kiln's colour suggestions. It is distinguishable from siblings like find_closest_filaments or fleet_colour_match, though it does not explicitly name those alternatives.

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 implied (record what a print actually came out as) and a prerequisite is supplied with 'Needs Kiln Pro.' However, there is no explicit guidance on when to use this versus other colour/filament tools, nor any exclusion conditions.

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