Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

G-code summary

gcode_summary
Read-onlyIdempotent

Reads print time, filament grams/metres/cost, layers, colour changes and key settings from an existing .gcode file so you can inspect slicer output without re-slicing.

Instructions

Read the numbers out of an existing .gcode file: print time, filament grams, metres and cost, layers, first-layer time, colour changes, key settings and metres extruded per feature type.

Use it on G-code you already have (from slice_model or another slicer); slice_model already returns these for new slices. Read-only.

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": "gcode_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to a .gcode file on this computer, e.g. one written by slice_model.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / path / description
      Added value: +"Path to a .gcode file on this computer, e.g. one written by slice_model."
  2. First observedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description's "Read-only" is largely redundant. It does add value by disclosing what the tool extracts and framing it as an inspection over pre-existing files rather than a re-slice, but it says nothing about behavior on a missing, truncated or malformed .gcode file, which is the main failure mode an agent would hit.

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?

Two tight paragraphs: the payload first, then routing guidance. Every clause carries information; the only redundancy is the trailing "Read-only", which repeats an annotation in three words.

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 takes on the return-value burden and discharges it by naming each extracted metric. Combined with the fully documented single parameter and rich annotations, an agent has everything needed to select and invoke it correctly.

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?

There is a single required parameter at 100% schema description coverage, which already states it is a path to a .gcode file on this computer. The description's "existing .gcode file" and the parenthetical about slice_model-written files only marginally extend that, so 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?

Opens with a specific verb and resource ("Read the numbers out of an existing .gcode file") and then enumerates the exact metrics returned (print time, filament grams/metres/cost, layers, first-layer time, colour changes, key settings, metres per feature). It explicitly separates itself from slice_model, so an agent can choose between them without inspecting either 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 an explicit when-to-use ("G-code you already have (from slice_model or another slicer)") and names the alternative plus its distinguishing condition ("slice_model already returns these for new slices"). Both the inclusion and the exclusion are stated, leaving nothing to infer.

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