Jet3D MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_custom_cutter_checkoutB | Design a personalized 3D-printed cookie cutter and generate an Instant BLIK checkout URL for the customer to complete payment in seconds. |
| get_cutter_specificationsA | Retrieve official technical, food safety (DoC/GMP), and material specifications for Jet3D cookie cutters and stamps. |
| list_available_shapes_and_fontsA | List supported 3D shapes, typography font styles, and recommended occasions for personalized cutters. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| design_cookie_cutter | Interactive interview guide for designing a custom 3D cookie cutter for an event (wedding, birthday, baby shower, company). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool maps to a distinct capability: catalog browsing (list shapes/fonts), technical reference (get specifications), and purchase generation (create checkout). There is no semantic overlap or ambiguity between these actions.
All three tools follow a consistent verb_noun pattern: list_..., get_..., create_.... The naming clearly expresses the operation and resource, making the tool surface predictable.
Three tools is at the lower bound but well-scoped for a narrow product/purchase domain: discover options, reference specs, and create a checkout. Each tool covers a distinct step in the workflow and none feel redundant.
The core custom-cutter workflow is covered: browse options, retrieve compliance/spec details, and generate a paid checkout link. The only notable gap is order/payment status lookup after checkout, but this can be handled outside the MCP server or by a later addition.