Skip to main content
Glama
spikeon

negative-support-mcp

by spikeon

negative_support_generate

Generate negative-space print supports for 3D models. Create STL or 3MF files from local STL, OBJ, STEP, or STP inputs, with configurable angle, gap, and volume.

Instructions

Generate support STL (and optionally 3MF with model + support pieces) from a local STL, OBJ, STEP, or STP file. Requires an activated license. Heavy meshes can take many minutes; MCP hosts that send a progressToken receive keepalive progress and avoid tool timeouts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
angleNoOverhang angle threshold in degrees (default 45)
formatNoFile format; default: inferred from extension
marginNoGap between supports and model in mm (default 0.2)
input_pathYesAbsolute path to the model file on the machine running this MCP server
min_volumeNoMinimum support piece volume in mm³ (default 1.0)
skip_mergeNoIf true, skip merging pieces (OOM fallback)
output_3mf_pathNoIf set, also writes a 3MF containing the model and support objects
output_stl_pathNoWhere to write the supports STL (default: <basename>_supports.stl next to input)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statsYes
progressNo
output_3mf_pathNo
output_stl_pathYes
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses the license requirement, long-running behavior, and progress token support to avoid timeouts. It does not detail error conditions or file write side effects, but the core behavioral traits are covered.

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?

The description is two sentences, front-loaded with the primary purpose and followed by critical usage context. Every sentence adds value with no fluff.

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?

The description covers the tool's purpose, license prerequisite, performance expectations, and output types. Given the 8 parameters and the presence of an output schema, it does not need to explain return values. It could mention error handling for missing license, but for a complex tool it is sufficiently complete.

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?

The input schema has 100% description coverage for all 8 parameters, so the baseline is 3. The description adds minimal extra semantics beyond the schema, only clarifying that the 3MF includes model and support pieces, which matches the schema descriptions.

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?

The description clearly states the tool's action: generate support STL (and optionally 3MF) from local model files. It specifies the input formats and distinguishes itself from the sibling activation/deactivation tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description notes that an activated license is required, which implicitly tells the agent to use 'negative_support_activate' first. It also provides guidance on heavy meshes and progress tokens, but it does not explicitly mention when not to use the tool or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/spikeon/negative-support-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server