Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_safety_profiles

Read-only

Lists printers with saved safety profiles by ID and name so you can choose the right printer ID for retrieving limits or validating G-code.

Instructions

List the printers Kiln has a safety profile for, by id and name.

        The list names printers; it carries no limits.  Kiln reads a
        printer's limits one printer at a time: call
        ``get_safety_profile`` with one of these ids for its temperature,
        feedrate and flow limits, its build volume, and where those
        numbers came from.  ``validate_gcode_safe`` checks commands
        against one printer's limits.  A printer set up on this machine
        with limits its owner entered is listed too, marked
        ``set_up_on_this_machine``.

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": "list_safety_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/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 safety profile is known. The description adds useful behavioral context beyond annotations: the list carries no limits, includes locally set-up printers marked set_up_on_this_machine, and points to the per-printer retrieval tool. It does not describe pagination or ordering, but the added context is substantial.

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 description is front-loaded with the core action and immediately clarifies that the list carries no limits. Each subsequent sentence adds useful routing or inclusion information. It is slightly longer than strictly necessary but remains well structured and free of filler.

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

Completeness5/5

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

With no input parameters, no output schema, and annotations covering safety, the description supplies everything an agent needs: what is returned (id and name), what is not returned (limits), how to get limits, and the special local-profile marker. No critical context is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is no parameter semantics to explain. The description appropriately focuses on what the returned ids are used for rather than inventing parameter details. Baseline for a zero-parameter tool is 4.

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

Purpose5/5

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

The description states a specific verb and resource: list printers for which Kiln has a safety profile, returning id and name. It explicitly distinguishes this from get_safety_profile, which retrieves limits for one printer, and from validate_gcode_safe, which checks commands. An agent can identify the tool's scope without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit routing: use this tool to obtain printer ids and names, then call get_safety_profile with one of those ids for limits. It also names validate_gcode_safe as the tool for checking commands against one printer's limits. The when-to-use and alternative-tool guidance is clear.

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