FormNord 3D printing

FormNord: pris på 3D-print

get_print_quote

Get an instant price for printing a 3D model (STL, 3MF, or a zip containing them, max 300 mm on the longest side) and shipping it within Norway. Provide exactly one of file_url, file_base64, stl_text, upload_id (from create_upload_link) or file_id. Returns tilbud_id (the quote_id), total price in NOK with breakdown, estimated weight and print time, and bestill_url: a page where the user can order themselves. To order on the user's behalf, use create_order. The quote is valid for 14 days.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`color`	No	PETG: Svart, Hvit, Grå, Blå, Grønn, Rød. ABS: Svart, Hvit. Default Svart.
`colors`	No	Multicolour 3MF (Bambu Studio/OrcaSlicer) only: one of our colour names per colour slot in the file, in slot order. Omit to get the nearest available colours (shown in fargeplasser).
`infill`	No	15 = light (lightning infill, 3 walls; maps, figures, decor), 20 = standard (most parts), 40 = strong (load-bearing), 100 = solid.
`file_id`	No	fil_id returned by POST https://formnord.no/api/print/fil (multipart upload), for clients that can send HTTP themselves.
`file_url`	No	Direct https link to an .stl, .3mf or .zip file up to 500 MB (not a web page about the model; Thingiverse/Printables pages block automated downloads, so use create_upload_link for those).
`filename`	No	File name, e.g. "holder.stl".
`material`	No	PETG is the default and suits most parts. ABS for heat resistance.	PETG
`quantity`	No
`stl_text`	No	ASCII STL content, for small models you generated.
`upload_id`	No	upload_id from create_upload_link, after the user has uploaded the file.
`zip_entry`	No	If the file is a zip with several models: which one to quote (name from the list in the previous error).
`file_base64`	No	The model file encoded as base64 (up to 30 MB; use create_upload_link for larger files).

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`kode`	No	Machine-readable error code when ok is false.
`pris`	No	Price breakdown in NOK; pris.totalt is the total including shipping.
`valg`	No	Present with kode zip_entry_required.
`grunn`	No	Human-readable reason (Norwegian) when ok is false.
`tilbud_id`	No	quote_id for create_order and get_quote_status.
`gyldig_til`	No
`upload_url`	No	Present with kode upload_pending.
`bestill_url`	No
`prisgrunnlag`	No
`slicing_status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 16, 2026

changedInput schema / properties / file_base64 / description

Previous value: -"The model file encoded as base64."New value: +"The model file encoded as base64 (up to 30 MB; use create_upload_link for larger files)."

changedInput schema / properties / file_url / description

Previous value: -"Direct https link to an .stl or .3mf file (not a web page about the model)."New value: +"Direct https link to an .stl, .3mf or .zip file up to 500 MB (not a web page about the model; Thingiverse/Printables pages block automated downloads, so use create_upload_link for those)."

First observedOct 16, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already flag openWorldHint=true, idempotentHint=false, destructiveHint=false, so the safety profile is partly covered. The description adds real value beyond that: the 14-day quote validity, that it does not place an order, and the 300 mm size constraint. It does not discuss rate limits or failure modes, so it stops short of a 5.

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?

Five tight sentences, front-loaded with purpose then constraints then return values, with zero filler. Slightly dense, but every sentence carries information.

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?

A no-required-parameter, 12-param tool with a 92% covered schema and an output schema present; the description supplies the missing cross-parameter rule, format constraints, and sibling routing. Nothing an agent needs to invoke it correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 92%, so the baseline is 3, but the description adds the cross-parameter rule ('provide exactly one of file_url, file_base64, stl_text, upload_id or file_id') and the 300 mm limit, which the schema does not state. That is meaningful semantics beyond the structured fields.

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+resource ('Get an instant price for printing a 3D model') with scope (Norway shipping, supported formats, size limit). An agent can immediately distinguish it from create_order and get_quote_status.

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?

Explicitly routes to create_order for ordering on the user's behalf, to create_upload_link for pages that block downloads, and states the one-of input constraint. When-to-use and alternatives are both covered.

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

All FormNord 3D printing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?