Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_maintenance_prediction

Read-only

Predicts when a specified 3D printer is likely to need maintenance, helping schedule upkeep before issues cause downtime. Requires Kiln Pro.

Instructions

Predict when maintenance is likely needed for a printer.

Needs Kiln Pro.

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": {
      "printer_id": "<printer_id>"
    },
    "name": "get_maintenance_prediction"
  }
}

Input Schema

NameRequiredDescriptionDefault
printer_idYesThe printer identifier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / printer_id / description
      Added value: +"The printer identifier."
  2. Addedv1.5.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly and non-destructive behavior, so the safety profile is covered. The description adds one genuinely useful operational fact beyond annotations: it requires a paid 'Kiln' Pro tier, which affects whether the agent should even attempt the call. It does not disclose what the prediction is based on, how far ahead it forecasts, or whether the result is advisory only.

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, purpose first, constraint second, with zero filler. The standalone 'Needs Kiln Pro' line is slightly terse but efficiently front-loads a blocking prerequisite.

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 one-parameter read-only prediction tool with no output schema, the definition leaves a real gap: nothing describes the shape of the prediction (time-to-maintenance estimate, confidence, recommended action), which the agent needs to interpret results. The tier prerequisite is a plus, but overall it is only minimally sufficient.

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?

There is a single required parameter and schema description coverage is 100%, so the schema already explains 'printer_id'. The description adds nothing about whether the ID is a local, fleet, or cloud identifier, but with full schema coverage the baseline of 3 is appropriate.

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: 'Predict when maintenance is likely needed for a printer.' An agent immediately understands it produces a maintenance-timing forecast for a given printer. However, it never distinguishes itself from the closely related sibling 'maintenance_due', so the agent must guess which of the two to call.

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?

The only guidance is the prerequisite 'Needs Kiln Pro', which tells the agent about a tier requirement but nothing about when this tool is the right choice versus 'maintenance_due', 'check_printer_health', or 'get_calibration_freshness'. There are no exclusions, no preconditions beyond tier, and no alternative routing.

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