Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

check_magnet_design

Read-only

Check a proposed printed magnet design for hidden failure modes, sizing and fit issues, and safety or environmental risks. Get warnings and validation guidance before printing or production.

Instructions

Check a proposed printed magnet design for hidden failure modes.

Free door, tiered answer — Free: Warnings — always free · Pro: Sizing and fit for the hardware you bought · Business: + Per-machine fit, validation tests and QC plans across your fleet · Enterprise: + Child-safety & supplier vetting for magnets.

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": {
      "use_case": "<use_case>"
    },
    "name": "check_magnet_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
coatingNoThe coating proposed, as the ``coating_id`` a magnet recommendation returns. Checked against a wet, outdoor or body-adjacent context; empty skips the check. Default: "".
use_caseYesProduct/use description, e.g. "removable access panel", "magnetic badge", "wall-mounted tool holder", "phone mount".
load_modeNopull, shear/slide, hanging, wall, gap/through plastic. Defaults to ``pull``; an unrecognised value is read as a direct pull. Default: "pull".
show_mathNoInclude non-identifying basis/confidence fields; never sources. Default: false.
commercialNoTrue for sold/customer/factory/production products. Default: false.
max_temp_cNoExpected maximum service temperature in degrees C, if known; omitted, no heat-margin check is made.
environmentNoindoor, humid, sweat, outdoor, hot_car, washdown, etc. Defaults to ``indoor``. Default: "indoor".
grade_classNoThe grade proposed, as the ``grade_class_id`` a magnet recommendation returns; a value naming N52 adds the "N52 is not automatically best" note. The heat-margin check runs only for a grade class id Kiln holds, together with ``max_temp_c``; empty skips it. Default: "".
has_air_gapNoTrue when a plastic cap, coating, adhesive, fabric, paint or tape sits between the magnet and its target, which adds an air-gap warning. Default: false.
adhesive_onlyNoTrue when the magnet is held by adhesive alone; flagged as not enough for a commercial, child-accessible or body-adjacent product. Default: false.
body_adjacentNoTrue for wearables, badges, phone/watch accessories, etc. Default: false.
magnet_familyNoThe magnet family proposed, e.g. "neodymium", "ferrite", "alnico". An alnico family is flagged for specialist review; empty, no family-specific check runs. Default: "".
child_accessibleNoTrue if children may access/mouth it. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv1.5.1
    • changedInput schema / properties / adhesive_only / description
      Previous value: -"Default: false."New value: +"True when the magnet is held by adhesive alone; flagged as not enough for a commercial, child-accessible or body-adjacent product. Default: false."
    • changedInput schema / properties / body_adjacent / description
      Previous value: -"Default: false."New value: +"True for wearables, badges, phone/watch accessories, etc. Default: false."
    • changedInput schema / properties / child_accessible / description
      Previous value: -"Default: false."New value: +"True if children may access/mouth it. Default: false."
    • changedInput schema / properties / coating / description
      Previous value: -"Default: \"\"."New value: +"The coating proposed, as the ``coating_id`` a magnet recommendation returns.  Checked against a wet, outdoor or body-adjacent context; empty skips the check. Default: \"\"."
    • changedInput schema / properties / commercial / description
      Previous value: -"Default: false."New value: +"True for sold/customer/factory/production products. Default: false."
    • changedInput schema / properties / environment / description
      Previous value: -"Default: \"indoor\"."New value: +"indoor, humid, sweat, outdoor, hot_car, washdown, etc. Defaults to ``indoor``. Default: \"indoor\"."
    • changedInput schema / properties / grade_class / description
      Previous value: -"Default: \"\"."New value: +"The grade proposed, as the ``grade_class_id`` a magnet recommendation returns; a value naming N52 adds the \"N52 is not automatically best\" note.  The heat-margin check runs only for a grade class id Kiln holds, together with ``max_temp_c``; empty skips it. Default: \"\"."
    • changedInput schema / properties / has_air_gap / description
      Previous value: -"Default: false."New value: +"True when a plastic cap, coating, adhesive, fabric, paint or tape sits between the magnet and its target, which adds an air-gap warning. Default: false."
    • changedInput schema / properties / load_mode / description
      Previous value: -"Default: \"pull\"."New value: +"pull, shear/slide, hanging, wall, gap/through plastic. Defaults to ``pull``; an unrecognised value is read as a direct pull. Default: \"pull\"."
    • changedInput schema / properties / magnet_family / description
      Previous value: -"Default: \"\"."New value: +"The magnet family proposed, e.g. \"neodymium\", \"ferrite\", \"alnico\".  An alnico family is flagged for specialist review; empty, no family-specific check runs. Default: \"\"."
    • addedInput schema / properties / max_temp_c / description
      Added value: +"Expected maximum service temperature in degrees C, if known; omitted, no heat-margin check is made."
    • changedInput schema / properties / show_math / description
      Previous value: -"Default: false."New value: +"Include non-identifying basis/confidence fields; never sources. Default: false."
    • addedInput schema / properties / use_case / description
      Added value: +"Product/use description, e.g. \"removable access panel\", \"magnetic badge\", \"wall-mounted tool holder\", \"phone mount\"."
  2. Addedv1.5.0

TDQS

B3.1/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 safety is covered. The description's one genuine addition is that the answer is tier-gated and that only the Free tier is guaranteed ("Warnings — always free"), which an agent needs to know because sizing and fit output may be withheld. It stops short of saying what a warning contains, how the tier is determined, or what happens when the check cannot run.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is tight and front-loaded. The second is a single run-on marketing line with middot-separated tier bullets that reads as pricing copy rather than tool documentation and is the longest part of the description despite carrying the least invocation-relevant detail.

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 13-parameter, read-only diagnostic with no output schema, the definition covers the purpose and the tier caveat, and the schema covers every field. It leaves open what the returned warnings look like, whether the checks are exhaustive, and how this fits in sequence with recommend_magnet_for_product or record_magnet_outcome, so an agent knows how to call it but not fully what to expect back.

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% across all 13 parameters, and those field descriptions already explain the semantics well (e.g. coating is a coating_id from a magnet recommendation, has_air_gap triggers an air-gap warning, grade_class needs a Kiln-held id for the heat-margin check). The prose adds nothing about parameters, 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 opening sentence gives a specific verb and resource: "Check a proposed printed magnet design for hidden failure modes." That is far clearer than the name alone, though it never distinguishes this check from neighbouring tools such as recommend_magnet_for_product, analyze_structural_risks or generate_magnet_qc_plan.

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 anywhere in the description. The second sentence lists what each subscription tier unlocks, which sets expectations about the answer's depth but says nothing about when an agent should call this tool versus the sibling recommendation, load-assessment or QC-plan tools.

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