Skip to main content
Glama

ai_modeling_print_open

Open an existing successful 3MF export in a compatible slicer or download its original ZIP/OBJ; plan-only by default, set execute to open or download.

Instructions

Hand an existing successful standalone 3MF export to a Studio-compatible slicer, or download an original export ZIP/OBJ. Defaults to plan only; execute=true explicitly opens/downloads to output_dir. No new export or print order is created.

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": {
      "task_id": "<task_id>",
      "target": "<target>"
    },
    "name": "ai_modeling_print_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
executeNoExplicitly allow opening the native slicer or downloading the original file. Omit to plan only.
task_idYesAn existing successful OBJ export for local or 3MF export for slicers; ZIP packages are downloaded only. No new export is created.
output_dirNoCaller-selected download directory for unsupported protocols or launch fallback.
artifact_idNoRequired when the export task contains multiple artifacts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the description's real contribution is the dry-run default, the execute gate, and the guarantee that no new export or print order is created. It does not mention that opening a native slicer leaves the process outside the tool's control, but the gating semantics are well disclosed.

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?

Three tight sentences, front-loaded with the core action and immediately followed by the safety-relevant default. The phrasing is dense ('Hand an existing successful standalone 3MF export') 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?

For a five-parameter, side-effecting tool with no output schema, the description covers the main risks: dry-run default, explicit execute, no artifact creation, and a download/launch fallback via output_dir. It omits what the plan-only response contains, which would help since no output schema exists.

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?

Schema coverage is 80%, so the schema already documents execute, task_id, output_dir and artifact_id. The description reinforces the plan-vs-execute distinction and groups targets as Studio-compatible slicers, but adds nothing about artifact_id selection or the enum members beyond what the schema states; baseline 3 applies.

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?

The description uses concrete verbs and resources: handing an existing 3MF export to a Studio-compatible slicer, or downloading an original export ZIP/OBJ. The closing clause 'No new export or print order is created' effectively separates it from export-creation and print-ordering siblings, though no sibling is named explicitly.

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 clearly states the entry condition (an existing successful export) and the default plan-only behavior, with execute=true as the explicit gate to act. It stops short of naming the alternative tools (e.g. a print-plan or print-shop sibling) that an agent should pick when no export exists.

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