Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Print card

print_card
Idempotent

Generate a shareable 1200x630 PNG summary card of sliced G-code with toolpath preview, time, filament, cost, layers, infill, walls, and printer details for quoting prints.

Instructions

Make a 1200x630 PNG summary card of a sliced print: toolpath preview, time, filament, cost, layers, infill, walls and printer.

Use it to share or quote a print; for inspecting toolpaths use preview_gcode. Writes _card.png next to the G-code, replacing an older one. Returns the image and its path.

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": {
      "path": "<path>"
    },
    "name": "print_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to a .gcode file on this computer, e.g. one written by slice_model.
titleNoHeading on the card. Default: the G-code file name.
price_per_kgNoFilament price per kg for the cost line. Default: the cost stored in the G-code.
currency_symbolNoSymbol shown before the cost, e.g. '$' or '€'.$

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false / idempotentHint=true; the description supplies the concrete side effect the agent needs: it writes '<name>_card.png' next to the G-code and replaces an older one, and it returns the image plus its path. That overwrite detail is behavior beyond the annotation set and is consistent with destructiveHint=false (it only clobbers its own prior output).

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 paragraphs, front-loaded with the artifact description followed by routing guidance and side effects; no filler. Minor deduction for the awkward hard-wrapped item list ('walls and printer' stranded on its own line) that reads as a formatting artifact rather than deliberate structure.

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?

With no output schema, the description correctly covers return values ('the image and its path'), and it covers the file-write location and overwrite semantics. For a 4-parameter tool with full schema coverage, nothing an agent needs before invoking is missing.

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 100%, so path, title, price_per_kg and currency_symbol are already fully documented, establishing a baseline of 3. The description only alludes to these indirectly by listing 'cost' among the card contents; it adds no formatting, unit or override-precedence detail beyond the 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?

States a specific verb ('Make') and a precisely specified artifact ('1200x630 PNG summary card of a sliced print'), then enumerates the exact contents (toolpath preview, time, filament, cost, layers, infill, walls, printer). An agent knows exactly what this produces and how it differs from screenshot/toolpath tools without reading the schema.

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

Usage Guidelines5/5

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

Gives a positive use case ('share or quote a print') and explicitly routes away to a named sibling for the other plausible intent: 'for inspecting toolpaths use preview_gcode'. The selection condition is unambiguous.

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