Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_community_wear_baseline

Read-only

Compare your nozzle's wear against Kiln community baselines for a specific filament, nozzle material, and printer model to judge maintenance and replacement needs.

Instructions

Pro+ — how nozzles like yours wear across the Kiln community.

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": {
      "filament_material": "<filament_material>",
      "nozzle_material": "<nozzle_material>",
      "printer_model": "<printer_model>"
    },
    "name": "get_community_wear_baseline"
  }
}

Input Schema

NameRequiredDescriptionDefault
printer_modelYesPrinter registry key (e.g. ``"bambu_a1"``).
nozzle_materialYesCurrently installed nozzle (e.g. ``"brass"``).
filament_materialYesFilament being printed (e.g. ``"PETG-CF"``).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / filament_material / description
      Added value: +"Filament being printed (e.g. ``\"PETG-CF\"``)."
    • addedInput schema / properties / nozzle_material / description
      Added value: +"Currently installed nozzle (e.g. ``\"brass\"``)."
    • addedInput schema / properties / printer_model / description
      Added value: +"Printer registry key (e.g. ``\"bambu_a1\"``)."
  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 readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the tool is gated behind Pro+ — but says nothing about aggregation method, sample size, data freshness, or what happens when no community cohort exists.

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?

A single front-loaded sentence with no filler, and the Pro+ gate is flagged first. It is arguably under-specified rather than overwritten, but nothing in it is wasted.

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 simple read-only lookup with well-described inputs and no output schema, the description is minimally sufficient to call the tool. It remains silent on what the baseline actually contains (wear rate, lifespan, percentiles) and on fallback behavior for sparse cohorts, which an agent would want before relying on the result.

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 the three parameters and their examples are fully documented in structured data. 'Nozzles like yours' adds the useful framing that the three inputs define a peer cohort for matching, but gives no detail on how matching works or whether partial matches are allowed.

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 phrase 'how nozzles like yours wear across the Kiln community' identifies a specific resource (community nozzle-wear baseline) scoped to the user's hardware and material profile, and the word 'community' implicitly separates it from get_my_nozzle_wear_patterns. It stops short of stating what metrics the baseline returns, and there is no verb, but an agent can still tell broadly what it retrieves.

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?

No when-to-use guidance, no stated alternatives (e.g. get_my_nozzle_wear_patterns for personal history, nozzle_wear_status for current state), and no conditions or exclusions. The only routing signal is the implied 'Pro+' gate, which is an entitlement note rather than usage direction.

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