Skip to main content
Glama
ttiimmaacc

mcp-for-clo3d

by ttiimmaacc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_pattern_sheet

Export 2D patterns as vector PDF or PNG for printing or plotting. Choose print layout or pattern window, paper size, orientation, and content layers to generate production-ready sheets.

Instructions

Export the 2D pattern as a PDF (vector, exactly 1:1: verified in CLO 2025.2) or PNG, by the file's extension, for plotting or printing.

"print_layout" exports the marker of the fabric shown in CLO's Print Layout Editor (see marker_report): the page is the fabric width by the marker length. It needs the layout set up once in CLO (Printing Layout mode, Auto Nesting). "pattern" exports the pattern window.

Args: file_path: Absolute path ending in .pdf or .png. source: "print_layout" or "pattern". paper: a4, a3, b5, b4, letter, legal, tabloid, wide_24in, wide_36in, wide_44in, one_to_one or custom (then give width_mm and height_mm). Default: CLO's setting. The PDF stays one 1:1 page whatever the paper (tested with a4: no tiling), so tile it with your plotter or PDF software for small paper. landscape: Paper orientation. width_mm: Paper width for custom paper. height_mm: Paper height for custom paper. resolution_dpi: Resolution for PNG output. show: What to draw, e.g. {"seam_allowance": true, "notches": true, "grain_line": true, "pattern_name": true, "annotations": true}. Keys: outline, internal_lines, graphic_outline, baseline, notches, seam_allowance, symmetry_line, reference_line, pattern_name, annotations, line_length, grain_line, button_holes, seam_taping, measurements_2d, grading_size_name, nest_information, fabric_texture, pattern_texture, graphic_texture.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
showNo
paperNo
sourceNoprint_layout
width_mmNo
file_pathYes
height_mmNo
landscapeNo
resolution_dpiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the vector 1:1 scaling, verification in CLO 2025.2, that PDF output stays as a single 1:1 page regardless of paper size (no tiling), and that print_layout depends on a prior CLO layout setup. It does not mention return values or error behavior, but the key 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 lengthy but every section earns its place: it front-loads the core behavior, then uses a clean Args block to document eight parameters. The extra notes about 1:1 scaling, paper behavior, and tiling are useful, not filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no annotations and no output schema, the description fully covers the operation, the two source workflows, prerequisites, all parameters, defaults, and paper behavior. An agent has enough to call this tool correctly for both PDF and PNG exports.

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 fully compensate, and it does. It explains file_path requirements, source values, all paper presets plus custom sizing, landscape, width/height, resolution_dpi, and the full show key set with an example object. This is far beyond what the bare input schema provides.

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 opens with a specific verb and resource: export the 2D pattern as PDF or PNG, and explains the format is chosen by file extension. It also distinguishes the two source modes (print_layout vs pattern), which separates it from related export tools like export_dxf, export_thumbnail, and export_snapshot.

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?

It gives clear context for when each source mode is appropriate: print_layout exports the marker from CLO's Print Layout Editor and requires one-time layout setup, while pattern exports the pattern window. It does not explicitly state when to choose this tool over sibling export tools, but the format and purpose are obvious enough that the lack is minor.

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

Deploy Server

Other Tools