Skip to main content
Glama
Sign In
CAD to Print MCP

CAD to Print MCP

by Kayrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

read_gcode_summary

Extract print time, filament usage, and layer counts from G-code or sliced 3MF files to verify slice settings before printing.

Instructions

Read available print time, filament, and layer metadata from G-code or sliced 3MF.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does add real value by declaring which file formats are accepted and by hedging that metadata is only 'available' (fields may be absent), but it says nothing about permissions, error behavior on unsliced files, or cost.

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?

A single front-loaded sentence naming the action, the returned data, and the accepted inputs, with zero filler.

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?

With only one parameter and an output schema already present to describe return values, the description needs little more. It covers the input formats and the data returned; only the path semantics and usage routing are thin.

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 0% and the single required 'path' parameter has no schema description. The description partially compensates by constraining the path to G-code or sliced 3MF artifacts, but it gives no format, relative-vs-absolute, or extension guidance.

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?

States a specific verb (read) plus the resource and the exact payload (print time, filament, layer metadata), and names the accepted inputs (G-code or sliced 3MF). It is clearly distinguishable from slicing siblings like run_slice or preview_slice, though it never names those siblings explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as preview_slice or get_printer_status. The only implicit signal is that a G-code/3MF artifact must already exist, which the agent has to infer.

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