Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

fleet_nozzle_agreement

Read-only

Find which registered 3D printers disagree with Kiln's nozzle record and rank the mismatches by priority.

Instructions

Which registered machines disagree with Kiln's nozzle record, and which matter first (Business).

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

Input Schema

NameRequiredDescriptionDefault
printer_namesNoWhich machines. Omit for every registered machine (each physical machine once). A name that is not registered is listed under ``not_registered`` and not swept.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / printer_names / description
      Added value: +"Which machines.  Omit for every registered machine (each physical machine once).  A name that is not registered is listed under ``not_registered`` and not swept."
  2. Addedv1.5.0

TDQS

C2.6/5.0
Behavior2/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 covered. The description adds nothing beyond that: it does not explain what "disagree" means, how "which matter first" is ordered, or what the response contains (no output schema exists).

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

Conciseness3/5

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

It is a single short sentence, but the question form plus the unexplained "(Business)" tag makes it cryptic rather than front-loaded; the wording hides the operation instead of stating it.

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 zero-required-parameter read-only query with no output schema, the description should at least sketch what comes back (agreement list plus priority ranking). It gestures at both but leaves the ranking criteria and result shape undefined.

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% and the printer_names schema description already explains the omit-for-all behavior and the not_registered fallback. The prose adds no additional meaning about the single optional parameter, so 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 identifies the resource (registered machines' nozzle records vs Kiln's record) and hints at a prioritization output, so the agent can roughly infer it is a comparison/audit query. But it is phrased as a question rather than a verb, and the trailing "(Business)" is opaque; nearby siblings like nozzle_wear_status, list_nozzle_states and get_my_nozzle_wear_patterns are not differentiated at all.

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?

There is no explicit when-to-use guidance, no prerequisites, and no named alternative among the many nozzle-related siblings (nozzle_wear_status, get_nozzle_state, auto_detect_nozzle). Usage is only implied by the question phrasing.

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