Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

find_slicer

Read-only

Detects an installed PrusaSlicer or OrcaSlicer on the system and returns its path, name, and version for 3D printing workflows.

Instructions

Check if a slicer (PrusaSlicer/OrcaSlicer) is available on the system.

Returns the slicer path, name, and version if found.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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 covered. The description earns some credit by disclosing the return payload (path, name, version), which matters because there is no output schema, but it omits what happens when nothing is found and what search scope (PATH vs common install directories) is used.

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?

Two short sentences, action first and return values second, with no filler. Every clause carries information an agent needs.

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 zero-parameter, read-only probe with full annotation coverage, the description plus annotations give an agent enough to invoke it correctly and interpret the response. The only gaps are edge-case behavior (not-found result, search locations), which are minor for this complexity.

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 nothing for the description to disambiguate beyond what the empty schema already conveys; the baseline of 4 applies. Nothing in the description misrepresents or muddies the parameter surface.

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 states a specific verb and resource ('Check if a slicer ... is available on the system') and narrows scope to PrusaSlicer/OrcaSlicer. It is clear what the tool does, but it does not distinguish itself from nearby siblings such as list_slicer_profiles or slice_model, which an agent could plausibly confuse with slicer discovery.

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: an agent can infer this is a pre-flight availability check, but the description never says when to call it versus alternatives (e.g. before slice_model or instead of list_slicer_profiles) or what to do if the result is negative. No exclusions or prerequisites are given.

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