Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_print_learning_summary

Read-only

Retrieve a printer's current learning summary to review material-specific outcomes, recovery history, and community insights.

Instructions

Get the current learning summary 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_print_learning_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialNoOptional material filter (e.g. "PLA", "PETG"). Default: "".
printer_idYesThe printer identifier (e.g. serial number or name).
failure_typeNoOptional failure context to use for recovery memory. Default: "".
include_recoveryNoInclude local recovery history when true. Default: true.
include_communityNoInclude anonymized community aggregates when true. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.5.1
    • changedInput schema / properties / failure_type / description
      Previous value: -"Default: \"\"."New value: +"Optional failure context to use for recovery memory. Default: \"\"."
    • changedInput schema / properties / include_community / description
      Previous value: -"Default: true."New value: +"Include anonymized community aggregates when true. Default: true."
    • changedInput schema / properties / include_recovery / description
      Previous value: -"Default: true."New value: +"Include local recovery history when true. Default: true."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"\"."New value: +"Optional material filter (e.g. \"PLA\", \"PETG\"). Default: \"\"."
    • addedInput schema / properties / printer_id / description
      Added value: +"The printer identifier (e.g. serial number or name)."
  2. Addedv1.5.0

TDQS

C2.8/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 a closed-world scope, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond them: the tool is gated behind a Kiln Pro tier. It says nothing about cost, latency, or whether results include cached/stale learning data.

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, front-loaded with the action and resource. The second sentence is clipped to the point of ambiguity ('Needs Kiln Pro' — a prerequisite for the call, for full results, or for the account?), which slightly undercuts clarity.

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

Completeness2/5

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

There is no output schema and five parameters including two inclusion flags, yet the description never says what a 'learning summary' contains or why recovery history and community aggregates are merged in. For an aggregation tool with no return-value contract documented anywhere, this leaves the agent unable to predict results.

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 printer_id, material, failure_type, include_recovery and include_community are all documented in the schema, including defaults and examples. The description adds no further semantics such as what material/failure_type filtering actually matches against the learned records, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Get') and a named resource ('learning summary for a printer'), but 'learning summary' is an undefined concept and nothing distinguishes this from adjacent tools such as get_printer_insights, get_recovery_strategy_stats, or get_proven_recipe. An agent can tell it is a per-printer read but not what makes this summary distinct.

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?

'Needs Kiln Pro' states an entitlement prerequisite rather than a usage condition; it does not say when to prefer this over the many other printer-insight tools. No alternatives or exclusions are named, so selection must be inferred from the tool name alone.

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