Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

ingest_material_datasheet

Extracts and verifies quoted datasheet values, then builds a structured material profile for 3D printing; optionally saves it to your library.

Instructions

Verify quoted datasheet values and build a structured material profile.

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_type": "<material_type>",
      "claims": "<claims>",
      "datasheet_text": "<datasheet_text>"
    },
    "name": "ingest_material_datasheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveNoPersist to your library when True. Default: false.
brandNoManufacturer, e.g. ``"Bambu Lab"``. Default: "".
claimsYesList of ``{"field", "raw", "source_span"}`` dicts.
productNoProduct line, e.g. ``"PLA Basic"``. Default: "".
source_urlNoWhere the datasheet came from. Default: "".
material_typeYesBase material, e.g. ``"pla"``, ``"petg"``.
datasheet_textYesThe text the claims were quoted from.
support_contactNoOptional contact for loop-back when the requested material ships. Omit to stay anonymous. Default: "".
support_urgencyNoOptional ``"whenever"`` / ``"soon"`` / ``"urgent"`` to accompany a first-class-support request. Default: "".
review_acknowledgedNoRequired True to save when any value is flagged as implausible -- forces a human re-check first. Default: false.
request_first_class_supportNoSet True to ask Kiln to add native support for this material (records a demand signal). Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.5.1
    • changedInput schema / properties / brand / description
      Previous value: -"Default: \"\"."New value: +"Manufacturer, e.g. ``\"Bambu Lab\"``. Default: \"\"."
    • addedInput schema / properties / claims / description
      Added value: +"List of ``{\"field\", \"raw\", \"source_span\"}`` dicts."
    • addedInput schema / properties / datasheet_text / description
      Added value: +"The text the claims were quoted from."
    • addedInput schema / properties / material_type / description
      Added value: +"Base material, e.g. ``\"pla\"``, ``\"petg\"``."
    • changedInput schema / properties / product / description
      Previous value: -"Default: \"\"."New value: +"Product line, e.g. ``\"PLA Basic\"``. Default: \"\"."
    • changedInput schema / properties / request_first_class_support / description
      Previous value: -"Default: false."New value: +"Set True to ask Kiln to add native support for this material (records a demand signal). Default: false."
    • changedInput schema / properties / review_acknowledged / description
      Previous value: -"Default: false."New value: +"Required True to save when any value is flagged as implausible -- forces a human re-check first. Default: false."
    • changedInput schema / properties / save / description
      Previous value: -"Default: false."New value: +"Persist to your library when True. Default: false."
    • changedInput schema / properties / source_url / description
      Previous value: -"Default: \"\"."New value: +"Where the datasheet came from. Default: \"\"."
    • changedInput schema / properties / support_contact / description
      Previous value: -"Default: \"\"."New value: +"Optional contact for loop-back when the requested material ships. Omit to stay anonymous. Default: \"\"."
    • changedInput schema / properties / support_urgency / description
      Previous value: -"Default: \"\"."New value: +"Optional ``\"whenever\"`` / ``\"soon\"`` / ``\"urgent\"`` to accompany a first-class-support request. Default: \"\"."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/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 agent knows this is a non-destructive, closed-world write. The description adds that values are verified and that a Kiln Business entitlement is required, but says nothing about what happens to flagged/implausible claims, what the save path does to the library, or that a support demand signal is recorded.

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 lines with the action front-loaded and the entitlement gate stated immediately after; nothing is padded. The fragmentary "Needs Kiln Business" is terse to the point of being slightly cryptic about what qualifies, but it is efficient.

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 an 11-parameter mutation-adjacent tool with no output schema, the description is thin: it does not describe the verification outcome, the review_acknowledged gating flow, or what is persisted when save is true. The rich schema compensates for parameter-level gaps, but the workflow an agent must orchestrate is left to be inferred.

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 all 11 parameters are already documented, including save, review_acknowledged, and the support fields; baseline 3 applies. The description's phrase "quoted datasheet values" loosely ties claims to datasheet_text but adds no syntax, format, or constraint details 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 pair ("Verify ... and build a structured material profile") against a named resource (datasheet values / material profile). An agent can distinguish it from list_ingested_materials or get_material_properties, though it never explicitly contrasts with the clearly related sibling read_material_datasheet.

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?

The only guidance is the gating prerequisite "Needs Kiln Business," which is useful but is a precondition rather than when-to-use guidance. There is no statement of when to prefer this over read_material_datasheet, lookup-type siblings, or list_ingested_materials, leaving the choice implied by the tool name alone.

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