Skip to main content
Glama
pzfreo

build123d-mcp

analyze_printability

Analyze a 3D model for FDM printability, checking overhangs, thin walls, watertightness, and bed fit to identify issues and improve print outcomes.

Instructions

Analyse a build123d shape for FDM printability using augura (BREP-exact analysis).

Checks: overhangs, manifold/watertight, tip-over risk, brim/raft need,
minimum vertical feature (→ max layer height), and thin walls. Optionally
checks bed-fit against a declared build volume.

Returns a plain-text summary followed by a JSON report with per-finding
detail (kind, severity, message, area/location where applicable).

object_name: named object from show() (default: current shape).
support_angle: faces shallower than this many degrees from horizontal need
    support (default 45).
nozzle: nozzle diameter in mm for wall-thickness check (default 0.4).
min_perimeters: walls thinner than min_perimeters × nozzle are flagged
    (default 2).
build_volume: optional build envelope as 'X Y Z' in mm, e.g. '256 256 256';
    omit to skip the bed-fit check.
bed_tol: Z tolerance in mm for identifying bed-contact faces (default 0.001);
    raise it for parts whose bottom faces sit slightly off Z=0.
min_feature: minimum vertical feature size in mm to flag (default 0.5).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nozzleNo
bed_tolNo
min_featureNo
object_nameNo
build_volumeNo
support_angleNo
min_perimetersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description bears the full burden. It discloses the return format (plain-text summary + JSON report), explains each parameter's effect, and lists checks performed. However, it does not explicitly state whether the tool is read-only or has side effects.

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?

The description is well-structured, starting with the overall purpose, then listing checks, return format, and parameter details. It is reasonably concise but could be slightly more streamlined; the parameter descriptions are clear but slightly verbose.

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?

Given 7 parameters (none required) and an output schema, the description covers all necessary information: tool purpose, checks, return format, and parameter meanings. It lacks error handling or prerequisite info but is otherwise complete for typical use.

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%, so the description must compensate. It does so thoroughly by explaining each parameter's meaning, unit, and default value (e.g., 'support_angle: faces shallower than this many degrees...'), adding significant value beyond the bare schema.

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 purpose: 'Analyse a build123d shape for FDM printability using augura (BREP-exact analysis).' It lists specific checks (overhangs, manifold, etc.) and distinguishes it from sibling tools like 'clearance' or 'measure' by focusing on printability.

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?

The description explains what the tool does but does not explicitly state when to use it versus alternatives. There are no 'when to use' or 'when not to use' statements, nor mention of alternative tools among siblings.

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/pzfreo/build123d-mcp'

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