Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

ingest_measurement

Destructive

Record a calibration measurement for a specific printer and material, then update that machine's calibration profile.

Instructions

Ingest a calibration measurement and update the per-machine profile.

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": {
      "measurement_kind": "<measurement_kind>",
      "payload": "<payload>",
      "printer_id": "<printer_id>",
      "material": "<material>"
    },
    "name": "ingest_measurement"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesThe measurement itself, a dict whose keys depend on ``measurement_kind`` (listed above), plus the optional tunable knobs. A non-dict is refused.
materialYesThe material the measured part printed in. Required for ``caliper`` and ``natural_language``; any placeholder for ``build_volume``.
printer_idYesThe printer the measurement was taken on, the key its calibration profile is kept under. Required.
measurement_kindYes``"caliper"``, ``"natural_language"`` or ``"build_volume"``, as described above. Any other value is refused with ``INVALID_INPUT``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • addedInput schema / properties / material / description
      Added value: +"The material the measured part printed in. Required for ``caliper`` and ``natural_language``; any placeholder for ``build_volume``."
    • addedInput schema / properties / measurement_kind / description
      Added value: +"``\"caliper\"``, ``\"natural_language\"`` or ``\"build_volume\"``, as described above.  Any other value is refused with ``INVALID_INPUT``."
    • addedInput schema / properties / payload / description
      Added value: +"The measurement itself, a dict whose keys depend on ``measurement_kind`` (listed above), plus the optional tunable knobs.  A non-dict is refused."
    • addedInput schema / properties / printer_id / description
      Added value: +"The printer the measurement was taken on, the key its calibration profile is kept under.  Required."
  2. Addedv1.5.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description is consistent with that by stating it updates the stored per-machine profile. However, it does not say what the update overwrites, whether prior calibration data is lost, or whether the change is reversible — exactly the context that destructiveHint=true makes important.

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?

A single front-loaded sentence with no filler, which is efficient. It is arguably undersized for a destructive, four-parameter, nested-payload tool, but nothing in it is wasted.

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?

Given a destructive mutation with a free-form nested payload and no output schema, the definition is minimally viable: the schema carries parameter detail and the annotations carry the safety profile. It still leaves unstated what the profile update means for existing calibration state, which an agent would want before calling a destructive 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?

Schema description coverage is 100%, so the schema already explains measurement_kind values, the payload's dependence on the kind, and material requirements per kind. The description adds no parameter-level meaning beyond that, which is the baseline expectation when the schema is this rich.

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 names a specific verb ('Ingest') and resource ('calibration measurement') and adds the consequential side effect ('update the per-machine profile'). It does not name or contrast with nearby siblings such as record_calibration_correction or import_third_party_calibration, so an agent must infer the boundary.

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?

There is no when-to-use or when-not-to-use guidance, and no indication of which of the three measurement kinds should be preferred in a given situation. The agent gets a purpose but no routing logic among the many calibration-related siblings.

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