Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

record_chemical_outcome

Log how a printed part performed when exposed to a chemical, capturing material, reagent, result, duration, and environment so Kiln can learn from real-world outcomes.

Instructions

Record how a printed part actually held up to a chemical -- so Kiln learns.

Needs Kiln Business.

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": {
      "material": "<material>",
      "reagent": "<reagent>",
      "result": "<result>"
    },
    "name": "record_chemical_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoAnything else worth capturing. Default: "".
resultYes"held" | "degraded" | "failed".
reagentYesWhat it was exposed to (e.g. "diesel", "bleach 5%").
durationNoHow long (e.g. "6 months", "7 days"). Default: "".
materialYesThe printed material (e.g. "PETG").
design_idNoDesign this part belongs to, if any. Default: "".
printer_idNoPrinter that made it. Defaults to "default". Default: "default".
environmentNoWhere/how (e.g. "submerged", "splash", "outdoor"). Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.5.1
    • changedInput schema / properties / design_id / description
      Previous value: -"Default: \"\"."New value: +"Design this part belongs to, if any. Default: \"\"."
    • changedInput schema / properties / duration / description
      Previous value: -"Default: \"\"."New value: +"How long (e.g. \"6 months\", \"7 days\"). Default: \"\"."
    • changedInput schema / properties / environment / description
      Previous value: -"Default: \"\"."New value: +"Where/how (e.g. \"submerged\", \"splash\", \"outdoor\"). Default: \"\"."
    • addedInput schema / properties / material / description
      Added value: +"The printed material (e.g. \"PETG\")."
    • changedInput schema / properties / notes / description
      Previous value: -"Default: \"\"."New value: +"Anything else worth capturing. Default: \"\"."
    • changedInput schema / properties / printer_id / description
      Previous value: -"Default: \"default\"."New value: +"Printer that made it. Defaults to \"default\". Default: \"default\"."
    • addedInput schema / properties / reagent / description
      Added value: +"What it was exposed to (e.g. \"diesel\", \"bleach 5%\")."
    • addedInput schema / properties / result / description
      Added value: +"\"held\" | \"degraded\" | \"failed\"."
  2. Addedv1.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write-but-not-destructive profile is covered. The description adds context beyond that: the record feeds Kiln's learning loop and the call requires a Kiln Business tier, which is a real gating condition an agent must know. It stops short of saying whether prior records can be amended or duplicated.

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, with the action and its purpose front-loaded and the prerequisite stated up front rather than buried. Every clause carries information and nothing is redundant.

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 an eight-parameter tool with full schema documentation and no output schema, the description covers purpose, the learning-loop effect, and the tier prerequisite, which is enough to call it correctly. The main remaining gap is what the tool returns or does on completion, which an agent may still want to know.

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%, with all eight fields individually documented including examples and defaults, so the schema carries parameter meaning. The description adds no additional semantics about required versus optional fields or valid result values.

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?

The description uses a specific verb (record) and an unambiguous resource (how a printed part held up to a chemical), so an agent knows this writes a real-world chemical exposure result. It does not name or contrast with adjacent tools such as check_chemical_resistance or the other record_*_outcome tools, so sibling differentiation is left implicit.

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?

"how a printed part actually held up" implies this is for post-exposure observation rather than prediction, which is useful framing. The only explicit condition is the hard prerequisite "Needs Kiln Business," and there is no statement of when not to use it or that check_chemical_resistance should be used for pre-exposure lookup instead.

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