Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

query_per_machine_offset

Read-only

Retrieve the stored calibration offset for a specific printer, material, feature class, and nominal size to correct feature dimensions before printing.

Instructions

Return the calibration offset for a specific feature.

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": {
      "printer_id": "<printer_id>",
      "material": "<material>",
      "feature_class": "<feature_class>",
      "nominal_size_mm": "<nominal_size_mm>"
    },
    "name": "query_per_machine_offset"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialYesThe material the offset applies to. Required.
printer_idYesThe printer whose offset to read. Required.
feature_classYesThe kind of feature (``hole``, ``pin``, ``slot``), as recorded by ``ingest_measurement``. Required.
nominal_size_mmYesThe feature's designed size in mm; the offset is kept per size, so a size no measurement was recorded at answers ``no_data``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • addedInput schema / properties / feature_class / description
      Added value: +"The kind of feature (``hole``, ``pin``, ``slot``), as recorded by ``ingest_measurement``. Required."
    • addedInput schema / properties / material / description
      Added value: +"The material the offset applies to.  Required."
    • addedInput schema / properties / nominal_size_mm / description
      Added value: +"The feature's designed size in mm; the offset is kept per size, so a size no measurement was recorded at answers ``no_data``."
    • addedInput schema / properties / printer_id / description
      Added value: +"The printer whose offset to read.  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?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the Kiln Pro tier requirement — but says nothing about the response shape or the no-data case for a lookup tool with no output schema.

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?

Two short sentences with the action stated first and the tier requirement isolated on its own line. No padding, though the requirement reads as a fragment rather than a complete constraint statement.

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 read-only single-value lookup the definition is adequate on inputs and access requirements. With no output schema, however, the description leaves the returned value undocumented, including the failure/empty-answer behavior that matters for a per-size offset lookup.

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 coverage is 100%, so all four parameters are documented in the schema, including the note that an unrecorded nominal size answers 'no_data'. The description adds nothing beyond that, so the baseline of 3 applies.

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 and resource ('Return the calibration offset') and narrows the scope to 'a specific feature'. An agent knows exactly what is being read, though it does not name how this differs from adjacent calibration tools such as get_calibration_freshness or apply_calibration_recommendations.

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?

'Needs Kiln Pro' is a prerequisite, not usage guidance. There is no statement of when to reach for this tool versus the many sibling calibration and recommendation tools, and no exclusion conditions given.

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