Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Estimate cost

estimate_cost
Read-onlyIdempotent

Calculate total 3D print cost from filament, electricity, and extra fees like labour or markup. Use it to generate quotes or answer what a print costs, returning each cost component and the total.

Instructions

Work out what a print costs: filament plus electricity plus any extra such as labour or markup.

Use it for quotes or when the user asks what something costs; compare_slices already reports filament cost per variant. Returns each part of the cost and the total. Read-only; pure arithmetic.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "estimate_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
extraNoFixed amount added, e.g. labour or markup.
gcodeNoPath to a sliced .gcode; supplies grams, time and filament price. Or give grams and print_time_s.
gramsNoFilament used in grams, when no gcode is given.
currencyNoCurrency label for the result, e.g. 'USD'.USD
price_per_kgNoFilament price per kg. Default: the price stored in the G-code.
print_time_sNoPrint time in seconds, when no gcode is given.
printer_power_wNoAverage printer power draw in watts.
electricity_per_kwhNoElectricity price per kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered; 'Read-only; pure arithmetic' largely restates that. What the description does add beyond structured data is the return shape ('each part of the cost and the total'), which matters since there is no output schema.

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?

Front-loaded with the purpose, then usage, then return shape, in three tight sentences. The closing 'Read-only; pure arithmetic' is mild redundancy against the annotations rather than wasted space.

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 pure-arithmetic calculator with all-optional parameters and full schema coverage, the description covers purpose, routing, and return composition. It does not note that the caller should supply either gcode or grams plus print_time_s, though the schema states that per-parameter.

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 description coverage is 100%, so every one of the eight parameters is already documented, including the gcode-versus-manual grams/print_time_s path and the default price sourced from G-code. The description adds no further meaning such as units, validation rules, or precedence between gcode and explicit grams.

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 and resource ('work out what a print costs') and enumerates the cost components (filament, electricity, extras like labour/markup). It also explicitly separates itself from compare_slices, so an agent can pick between them without opening 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 concrete triggering contexts ('for quotes or when the user asks what something costs') and names the alternative with its distinguishing behavior ('compare_slices already reports filament cost per variant'). When-to-use and when-to-use-something-else are both present.

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