Skip to main content
Glama

drying_advisor

Read-only

Check if a filament spool is dry enough to print, then get a targeted drying recipe, readiness verdict, or forecast for the selected tray or material.

Instructions

Is this spool ready to print -- and if not, exactly how to dry it?

Needs Kiln Pro.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "drying_advisor"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo``verdict`` (default, the collapsed answer) | ``recipe`` | ``readiness`` | ``forecast``. Changes only what is shown -- the numbers are identical across modes. Default: "verdict".
slotNoTray slot to read.
ams_idNoAMS unit index (0-based) to read.
materialNoAsk about a specific material (e.g. ``"PA6-CF"``) instead of the loaded tray. Default: "".
show_mathNoSurface the engineering detail (Tg, softening point, absorption %, per-field confidence, sources). Off by default -- plain English for every tier. Default: false.
printer_nameNoTarget printer. Omit for the default printer. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.5.1
    • addedInput schema / properties / ams_id / description
      Added value: +"AMS unit index (0-based) to read."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"\"."New value: +"Ask about a specific material (e.g. ``\"PA6-CF\"``) instead of the loaded tray. Default: \"\"."
    • changedInput schema / properties / mode / description
      Previous value: -"Default: \"verdict\"."New value: +"``verdict`` (default, the collapsed answer) | ``recipe`` | ``readiness`` | ``forecast``.  Changes only what is shown -- the numbers are identical across modes. Default: \"verdict\"."
    • changedInput schema / properties / printer_name / description
      Previous value: -"Default: \"\"."New value: +"Target printer.  Omit for the default printer. Default: \"\"."
    • changedInput schema / properties / show_math / description
      Previous value: -"Default: false."New value: +"Surface the engineering detail (Tg, softening point, absorption %, per-field confidence, sources).  Off by default -- plain English for every tier. Default: false."
    • addedInput schema / properties / slot / description
      Added value: +"Tray slot to read."
  2. Addedv1.5.0

TDQS

A3.6/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 agent knows this is a safe local read operation. The description adds the important Kiln Pro entitlement requirement, but does not elaborate on the return shape, confidence or limitations beyond what the question implies. With annotations covering much of the safety profile, this is adequate but not rich.

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

Conciseness5/5

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

The description is two short sentences, front-loaded with the core question and followed by the entitlement prerequisite. There is no wasted wording; every phrase contributes to understanding what the tool answers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only advisory tool with six optional, fully described parameters and no output schema, the description is complete enough. It conveys the core verdict/drying-guidance purpose and the Kiln Pro prerequisite. It could go further by naming the distinction from ams_filament_drying, but no essential prerequisite is missing.

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 the input schema already explains mode, slot, ams_id, material, show_math, and printer_name in detail. The description itself adds no parameter-level meaning beyond 'this spool'. The baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly frames the tool as a readiness check for a spool and a drying advisor: 'Is this spool ready to print -- and if not, exactly how to dry it?' It names the resource (spool) and the two outputs (print readiness verdict and drying instructions). It does not explicitly distinguish itself from the sibling action tool ams_filament_drying, which performs drying rather than advising, so a 4 rather than 5 is appropriate.

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 description supplies a prerequisite ('Needs Kiln Pro'), which is useful context for when the tool is available. However, it does not say when to use this advisor versus ams_filament_drying or ams_status, nor does it state exclusions. Usage is implied by the question form rather than explicitly guided.

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