Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

recommend_magnet_for_product

Read-only

Recommends a magnet strategy for a printed product, covering sizing, fit, validation, and tier-based guidance.

Instructions

Recommend a magnet strategy for a printed product, with tier-gated depth.

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": "recommend_magnet_for_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. Default: "pull".
show_mathNoInclude non-identifying basis/confidence fields; never sources. Default: false.
commercialNoTrue for sold/customer/factory/production products. Default: false.
complianceNoRequest compliance/regulatory path depth. Default: false.
max_temp_cNoExpected maximum service temperature in degrees C, if known.
environmentNoindoor, humid, sweat, outdoor, hot_car, washdown, etc. Default: "indoor".
body_adjacentNoTrue for wearables, badges, phone/watch accessories, etc. Default: false.
print_materialNoPrinted material, e.g. PLA, PETG, ASA, Nylon. Default: "".
strong_magnetsNoTrue for rare-earth/large/multiple strong magnets. Default: true.
supplier_packetNoRequest supplier declaration/packet depth. Default: false.
target_materialNoWhat the magnet pulls against, if known. Default: "".
child_accessibleNoTrue if children may access/mouth it. Default: false.
multiple_magnetsNoTrue if more than one magnet can become loose. Default: false.
current_supply_chainNoRequest current rare-earth/supply-chain depth. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv1.5.1
    • 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 / commercial / description
      Previous value: -"Default: false."New value: +"True for sold/customer/factory/production products. Default: false."
    • changedInput schema / properties / compliance / description
      Previous value: -"Default: false."New value: +"Request compliance/regulatory path depth. Default: false."
    • changedInput schema / properties / current_supply_chain / description
      Previous value: -"Default: false."New value: +"Request current rare-earth/supply-chain depth. Default: false."
    • changedInput schema / properties / environment / description
      Previous value: -"Default: \"indoor\"."New value: +"indoor, humid, sweat, outdoor, hot_car, washdown, etc. Default: \"indoor\"."
    • changedInput schema / properties / load_mode / description
      Previous value: -"Default: \"pull\"."New value: +"pull, shear/slide, hanging, wall, gap/through plastic. Default: \"pull\"."
    • addedInput schema / properties / max_temp_c / description
      Added value: +"Expected maximum service temperature in degrees C, if known."
    • changedInput schema / properties / multiple_magnets / description
      Previous value: -"Default: false."New value: +"True if more than one magnet can become loose. Default: false."
    • changedInput schema / properties / print_material / description
      Previous value: -"Default: \"\"."New value: +"Printed material, e.g. PLA, PETG, ASA, Nylon. Default: \"\"."
    • changedInput schema / properties / show_math / description
      Previous value: -"Default: false."New value: +"Include non-identifying basis/confidence fields; never sources. Default: false."
    • changedInput schema / properties / strong_magnets / description
      Previous value: -"Default: true."New value: +"True for rare-earth/large/multiple strong magnets. Default: true."
    • changedInput schema / properties / supplier_packet / description
      Previous value: -"Default: false."New value: +"Request supplier declaration/packet depth. Default: false."
    • changedInput schema / properties / target_material / description
      Previous value: -"Default: \"\"."New value: +"What the magnet pulls against, if known. Default: \"\"."
    • 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

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, closed-world behavior, and the description adds a genuinely non-obvious trait: response depth is gated by subscription tier, so a Free call returns only warnings while Pro/Business/Enterprise progressively unlock sizing, fleet validation and supplier vetting. What it omits is any signal about how the many depth flags (compliance, supplier_packet, current_supply_chain, show_math) interact with or override the tier, which is exactly the behavior an agent needs to predict output.

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 sentences, front-loaded with the core purpose, and the tier ladder is compactly encoded with bullet separators. The second sentence is dense but earns its space since tier gating is not derivable from any structured field.

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?

With 15 parameters and no output schema, the description needs to convey what a 'magnet strategy' looks like and roughly how inputs shape it; instead it delivers only the tier ladder. Annotations cover safety, so the main remaining gap is output shape and the mapping from inputs like load_mode and environment to recommendations.

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 every one of the 15 parameters is already documented with descriptions and defaults, which sets the baseline at 3. The description adds only an indirect hint that child_accessible and supplier_packet likely require Enterprise, but explains nothing about use_case, load_mode, environment, print_material or max_temp_c and how these drive the recommendation.

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: 'Recommend a magnet strategy for a printed product', which is unambiguous about what the tool returns. It does not differentiate itself from close siblings such as check_magnet_design, generate_magnet_qc_plan, review_magnet_supplier_packet, or recommend_hardware_pocket, so an agent cannot tell from the description alone which magnet-related tool to pick.

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 tier breakdown implies that any printed product needing magnet selection is in scope, but there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives. The bulk of the text describes entitlement tiers rather than selection criteria, so the agent must infer the intended trigger from the name.

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