Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

record_magnet_outcome

Log whether a magnet mount held, failed, or partially held, capturing magnet family, retention method, environment, and optional design notes for tracking retention performance.

Instructions

Record whether a magnet actually held (Pro). Prefer record_hardware_outcome.

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": {
      "family": "<family>",
      "retention_method": "<retention_method>",
      "result": "<result>"
    },
    "name": "record_magnet_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional free-text notes. Default: "".
familyYesMagnet family used, e.g. "neodymium", "ferrite", "N52".
resultYes``"held"``, ``"failed"``, or ``"partial"``.
design_idNoOptional design id to link this outcome to. Default: "".
load_modeNoOptional free-text load description. Default: "".
printer_idNoOptional printer id. Default: "".
environmentNoFree-text service environment, e.g. "outdoor", "hot car", "indoor". Default: "".
retention_methodYesHow it was mounted, e.g. "mechanical", "adhesive", "pocket".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.5.1
    • changedInput schema / properties / design_id / description
      Previous value: -"Default: \"\"."New value: +"Optional design id to link this outcome to. Default: \"\"."
    • changedInput schema / properties / environment / description
      Previous value: -"Default: \"\"."New value: +"Free-text service environment, e.g. \"outdoor\", \"hot car\", \"indoor\". Default: \"\"."
    • addedInput schema / properties / family / description
      Added value: +"Magnet family used, e.g. \"neodymium\", \"ferrite\", \"N52\"."
    • changedInput schema / properties / load_mode / description
      Previous value: -"Default: \"\"."New value: +"Optional free-text load description. Default: \"\"."
    • changedInput schema / properties / notes / description
      Previous value: -"Default: \"\"."New value: +"Optional free-text notes. Default: \"\"."
    • changedInput schema / properties / printer_id / description
      Previous value: -"Default: \"\"."New value: +"Optional printer id. Default: \"\"."
    • addedInput schema / properties / result / description
      Added value: +"``\"held\"``, ``\"failed\"``, or ``\"partial\"``."
    • addedInput schema / properties / retention_method / description
      Added value: +"How it was mounted, e.g. \"mechanical\", \"adhesive\", \"pocket\"."
  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 write-and-safety profile is covered structurally. The description's only additional signal is "(Pro)", which usefully flags a tier gate the annotations do not express. It says nothing about persistence, whether entries are idempotent, or what happens to linked design/printer ids.

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 core action front-loaded and zero filler. The second sentence is terse enough to be slightly cryptic, but nothing is redundant.

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 eight-parameter write tool with no output schema, the description is thin: it does not explain what the recorded outcome is used for or how it relates to sibling outcome-recording tools such as record_load_outcome and record_bond_outcome. The schema fully documents inputs, and annotations cover safety, so nothing is broken — but the routing and purpose context is minimal.

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 eight parameters, including the required family, retention_method, and result, are already documented with examples and defaults. The description adds no field-level meaning beyond the schema. Baseline 3 applies when the schema carries the burden.

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 and resource: recording whether a magnet held, with the retention context implied by the title. It also names a sibling (record_hardware_outcome), so an agent can distinguish it from the generic hardware-outcome tool. It stops short of describing what the record feeds into or how it differs in scope from that sibling.

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?

"Prefer record_hardware_outcome" is the only routing guidance, and it is a bare directive without a condition — it does not say when a magnet-specific outcome is warranted over the generic one. There are no prerequisites or exclusions stated. Usage is implied rather than explained.

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