Skip to main content
Glama
creator5-slicer-mcp

creator5-slicer-mcp

by rsutcliffe

list_filaments

Lists filament types the server understands and installed Creator 5 presets for a given nozzle size and Pro status, helping you choose compatible materials before slicing.

Instructions

List the filament types this server understands and the Creator 5 presets installed.

Args: nozzle: Nozzle diameter in mm: 0.25, 0.4, 0.6 or 0.8. pro: True for the Creator 5 Pro.

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

Input Schema

NameRequiredDescriptionDefault
proNo
nozzleNo0.4

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that the returned set is hardware/profile-dependent — the list changes with nozzle diameter and the Pro flag — which is real behavioral context beyond the schema. However, it says nothing about whether the operation is read-only, how results are ordered or structured, or whether the presets list is filtered.

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?

One front-loaded sentence stating purpose and output content, followed by a compact Args block. Nothing is redundant and nothing important is buried.

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 two-optional-parameter read tool with no output schema and no annotations, the description covers purpose, the hardware-dependent variation in results, and per-parameter meaning. It could go further by stating that it is a safe, side-effect-free lookup or describing what a returned entry contains, but the essential call information is present.

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?

Schema description coverage is 0% and the nozzle parameter is an unconstrained string with no enum, so the description does essential work by enumerating the legal diameters (0.25, 0.4, 0.6, 0.8) and explaining that pro selects the Creator 5 Pro variant. It omits the defaults (0.4, false) that the schema already supplies, which is acceptable.

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 names a specific verb and resource ("List the filament types") and adds scope detail — server-understood types plus Creator 5 installed presets — which distinguishes it from siblings like recommend_settings or analyse_model. It never states what it is *not* for, but an agent can tell it apart from the other catalog tools.

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 mention of alternatives. The natural workflow (call this first to discover valid filament identifiers before recommend_settings or slice_model) is only implied and never stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.