Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

find_printers_with_material

Read-only

Find 3D printers loaded with a specified material, with optional color and minimum-gram filters; results are sorted by remaining stock.

Instructions

Find printers that have a specific material loaded.

        Returns printers with the matching material, sorted by
        remaining stock (most first).  Optionally filter by colour
        and minimum remaining grams.

        Args:
            material_type: Material type to find (e.g. ``"PLA"``).
            color: Optional colour filter.
            min_grams: Minimum remaining grams (default 0).

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": {
      "material_type": "<material_type>"
    },
    "name": "find_printers_with_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoOptional colour filter.
min_gramsNoMinimum remaining grams (default 0). Default: 0.0.
material_typeYesMaterial type to find (e.g. ``"PLA"``).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / color / description
      Added value: +"Optional colour filter."
    • addedInput schema / properties / material_type / description
      Added value: +"Material type to find (e.g. ``\"PLA\"``)."
    • changedInput schema / properties / min_grams / description
      Previous value: -"Default: 0.0."New value: +"Minimum remaining grams (default 0). Default: 0.0."
  2. Changed3 schema fields changedv1.5.0
    • removedInput schema / properties / color / default
      Removed value: -null
    • removedInput schema / properties / min_grams / default
      Removed value: -0
    • addedInput schema / properties / min_grams / description
      Added value: +"Default: 0.0."
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without help. The description does add one piece of non-annotated behavior — results are sorted by remaining stock, most first — but says nothing about pagination, empty-result handling, or which printer fleet is searched.

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?

The core sentence is front-loaded and the sorting guarantee follows immediately, so an agent skimming the first line gets the essentials. The trailing Args block is largely duplication of the input schema and could be dropped without loss.

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?

With only three params, no nested objects, and no output schema, the description usefully sketches the return shape (printers with the matching material, ordered by remaining stock). That compensates for the missing output schema; only the scope of the printer set and pagination remain unspecified.

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 three parameters are documented in the schema, and the description's Args block essentially restates those same strings rather than adding meaning. The one modest addition is clarifying that min_grams filters on remaining stock, which is consistent with the sort behavior.

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 opens with a specific verb+resource: 'Find printers that have a specific material loaded', which is unambiguous about what is queried. It does not, however, distinguish itself from nearby siblings such as find_closest_filaments, check_printer_material_support, or get_fleet_material_summary, leaving the agent to infer the boundary.

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?

Usage is only implied: 'Optionally filter by colour and minimum remaining grams' tells the agent what can be narrowed but never when this tool should be chosen over a sibling or what preconditions apply. No explicit exclusions or alternatives are named.

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