Skip to main content
Glama
creator5-slicer-mcp

creator5-slicer-mcp

by rsutcliffe

check_setup

Checks whether the slicer, Creator 5 presets, and printer connection are ready before slicing or printing.

Instructions

Report whether the slicer, its Creator 5 presets and the printer connection are ready.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does disclose the scope of the check (three named components), which is genuine content beyond a bare label. It does not state that the operation is side-effect-free, whether a partial failure raises an error or is reported in the result, or whether any setup/auth is required before it can run. For a diagnostic tool this is adequate but thin.

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 no filler; the scope of the check is presented immediately. Nothing can be trimmed without losing information.

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?

With no output schema and no annotations, the description is the only source of truth, and it leaves the return shape ambiguous: an agent cannot tell whether it receives one aggregate ready/not-ready verdict or a per-component breakdown, nor what a failure of only one component looks like. That matters for a tool whose entire value is the report it produces.

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 are no arguments to disambiguate and the baseline is 4. Nothing in the description misrepresents the empty argument object.

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 specific verb ('report whether ... are ready') and enumerates the three resources inspected: the slicer, its Creator 5 presets, and the printer connection. This is clearly a composite pre-flight diagnostic, distinct from single-target siblings like slice_model or send_to_printer. It does not, however, explicitly say how it differs from printer_status, which covers an overlapping domain.

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?

The description never says when to call this tool, whether it is a prerequisite for slice_model/send_to_printer, or how it relates to printer_status. The pre-flight intent is only inferable from the name and the word 'ready'. No exclusions or alternatives are offered.

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