Skip to main content
Glama
creator5-slicer-mcp

creator5-slicer-mcp

by rsutcliffe

analyse_model

Measure STL size, volume, bed contact, overhangs, and 256 mm bed fit to verify printability before slicing.

Instructions

Measure an STL: size, volume, bed contact, overhangs and whether it fits the 256 mm bed.

Args: model_path: Absolute path to the model file on this computer.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model_path": "<model_path>"
    },
    "name": "analyse_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden; "measure" strongly implies a non-destructive read, and the hardcoded 256 mm bed constant is useful operational context. It does not state what happens on a missing/invalid file, whether it is cheap to call repeatedly, or whether the result is cached, so it only partially fulfills the burden.

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

Conciseness4/5

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

One front-loaded sentence lists the outputs before the args, and the args block is brief. The "Args:" header is slightly heavy for a single parameter, but no sentence is wasted.

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?

No output schema exists, so the description's enumeration of returned metrics does the necessary work of describing the result. For a one-parameter read tool it is nearly complete; only error behavior and output format detail are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description fully compensates: it specifies that model_path must be absolute and refers to a file on this computer, clarifying local-filesystem addressing. That is meaningful semantics beyond a bare "string" typed property.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Measure an STL" pairs a specific verb with a specific resource, then enumerates exactly what is measured: size, volume, bed contact, overhangs, and 256 mm bed fit. This is clearly distinguishable from the sibling slice_model, which would produce g-code rather than measurements.

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 statement of when to use this versus slice_model, check_setup, or recommend_settings. The listed measurements imply a pre-slicing check, but the agent must infer that workflow entirely; there are no stated prerequisites or exclusions.

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