Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_nozzle_states

Read-only

Lists all printers with a recorded nozzle state so you can identify machines that have saved nozzle data.

Instructions

List every printer with a recorded nozzle state.

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_nozzle_states"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.7/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 openWorldHint=false, so the safety profile is fully covered before the description is read. The description adds only a light scoping detail (only printers with a recorded state appear), and with no output schema it says nothing about what a record contains or how missing-state printers are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the resource and scope stated immediately and no filler. Nothing in it is redundant with the name or annotations in a wasteful way.

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?

For a trivial, zero-argument, read-only listing tool with annotations carrying the safety profile, the description covers the essential scope. The one remaining ambiguity, what fields each returned printer/nozzle record includes, is mild given the absence of an output schema and the simplicity of the operation.

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 takes zero parameters, so there is no parameter semantics to explain and the baseline applies. The description does not add filtering or formatting detail, but none is needed for a no-argument call.

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?

States a concrete verb plus resource and adds a meaningful scope qualifier: enumerate printers that have a recorded nozzle state. This is clear on its own, but it makes no reference to the obviously related siblings (get_nozzle_state, set_nozzle_state, nozzle_wear_status), so an agent must infer the difference between a per-printer lookup and this enumeration.

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?

The phrase 'every printer' implies a broad-enumeration use case as opposed to a single-printer lookup, which is a reasonable hint. However, there is no explicit statement of when to use this instead of get_nozzle_state, nor any note about prerequisites or exclusions, leaving routing to inference.

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