Skip to main content
Glama

record_decoration_preset_outcome

Records a print outcome (success, partial, or failed) against a specific decoration preset version, so each version builds its own track record for quality and adhesion analysis.

Instructions

Record a print outcome against a specific preset version.

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": {
      "preset_version_id": "<preset_version_id>",
      "print_job_id": "<print_job_id>",
      "outcome": "<outcome>"
    },
    "name": "record_decoration_preset_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoFreeform operator notes. Appended after the structured prefix.
outcomeYesOne of ``"success"``, ``"partial"``, ``"failed"``; any other word is refused.
mesh_pathNoOptional path to the printed STL. When a ``<mesh>.intent.json`` sidecar lives next to it, ``intent_id`` / ``intent_hash`` are auto-tagged on the outcome row so per-intent success-rate queries pick this print up without the caller threading them by hand.
print_job_idYesIdentifier of the print job that produced this outcome. Stored alongside the outcome so the print can be traced back later.
quality_scoreNoOptional 0.0–1.0 subjective quality rating. Packed into the notes prefix.
adhesion_qualityNoOptional one of ``"poor"``, ``"good"``, ``"excellent"``. Maps to ``adhesion_issues=(adhesion_quality == "poor")`` on the underlying row and is also preserved verbatim in the notes prefix for round-trip.
preset_version_idYesThe preset version attached at print time. Outcomes are keyed per-version so a version bump starts a clean track record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.5.1
    • addedInput schema / properties / adhesion_quality / description
      Added value: +"Optional one of ``\"poor\"``, ``\"good\"``, ``\"excellent\"``.  Maps to ``adhesion_issues=(adhesion_quality == \"poor\")`` on the underlying row and is also preserved verbatim in the notes prefix for round-trip."
    • addedInput schema / properties / mesh_path / description
      Added value: +"Optional path to the printed STL.  When a ``<mesh>.intent.json`` sidecar lives next to it, ``intent_id`` / ``intent_hash`` are auto-tagged on the outcome row so per-intent success-rate queries pick this print up without the caller threading them by hand."
    • addedInput schema / properties / notes / description
      Added value: +"Freeform operator notes.  Appended after the structured prefix."
    • addedInput schema / properties / outcome / description
      Added value: +"One of ``\"success\"``, ``\"partial\"``, ``\"failed\"``; any other word is refused."
    • addedInput schema / properties / preset_version_id / description
      Added value: +"The preset version attached at print time.  Outcomes are keyed per-version so a version bump starts a clean track record."
    • addedInput schema / properties / print_job_id / description
      Added value: +"Identifier of the print job that produced this outcome.  Stored alongside the outcome so the print can be traced back later."
    • addedInput schema / properties / quality_score / description
      Added value: +"Optional 0.0–1.0 subjective quality rating.  Packed into the notes prefix."
  2. Addedv1.5.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare this is a non-read-only, non-destructive, closed-world write. The description adds useful entitlement context with 'Needs Kiln Pro,' but does not explain duplicate handling, validation failures, or persistence behavior beyond what the schema covers.

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 purpose front-loaded and the entitlement requirement clearly separated. There is no unnecessary wording.

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?

The rich schema and annotations make the definition workable, but the description is thin for a mutation tool in a crowded namespace of similar record_* tools. It lacks routing guidance and operational context about what recording an outcome entails.

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 the schema already documents all seven parameters thoroughly. The description only reinforces the preset-version scope and adds no syntax, defaults, or constraints beyond the schema.

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 a print outcome' scoped 'against a specific preset version.' It implies a distinction from generic outcome tools, but does not explicitly name alternatives such as record_print_outcome or record_decoration_success.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage guidance is the 'Needs Kiln Pro' prerequisite. It does not say when to use this versus sibling outcome-recording tools, when not to use it, or whether the preset version must already exist or be released.

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