Skip to main content
Glama

ai_modeling_print_plan

Read-only

Plan delivery of an existing 3MF export to a slicer or an OBJ/ZIP download, returning routing metadata and required parameters without creating files or opening apps.

Instructions

Plan handing an existing standalone 3MF export to a slicer or downloading an existing OBJ/export ZIP. Returns metadata, never signed URLs; does not export, download, or open an app.

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_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false; the description adds the important nuance that the result is metadata only and never contains signed URLs, which prevents an agent from expecting a usable download link. It does not say whether planning reserves anything or whether the plan expires, but the key safety-relevant behavior is disclosed and consistent with the annotations.

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?

Two tight sentences with no filler, and the negative scope statement is packed into the second half where it constrains expectations efficiently. The opening clause 'Plan handing an existing standalone 3MF export...' is slightly dense but still front-loads the purpose.

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 read-only planning tool with no output schema, the description tells the agent enough: what input state is required (an existing export), what comes back (metadata, not signed URLs), and what will not happen (no export, download, or app launch). The shape of the returned plan is left unstated, which is the only meaningful gap.

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 75% and the schema itself explains task_id (must be an existing successful OBJ/3MF export, no new export created), output_dir, and artifact_id. The description adds no parameter-level detail, and the target enum in particular has no schema description, so the description does not compensate for the remaining gap. Baseline 3 applies.

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 names a specific verb (plan) and concrete resources (handing an existing 3MF export to a slicer, or an existing OBJ/export ZIP), and explicitly negates adjacent behaviors: 'does not export, download, or open an app.' That negation cleanly separates it from siblings like ai_modeling_print_open and ai_modeling_artifact_download without needing their schemas.

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 states the situation that selects this tool: an export already exists and the caller needs a handoff/download plan rather than the action itself. The exclusions ('does not export, download, or open an app') implicitly route the agent to the acting tools, but no alternative is named outright, so it stops short of a full when/when-not/alternatives statement.

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