com.printyourduck/quote
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRINTYOURDUCK_MCP_ALLOWED_ROOTS | No | Path-delimited allowlist of additional project directories for local file discovery and upload. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_printyourduck_quote_requirementsA | Read public requirements for a PrintYourDuck manual custom 3D printing quote request. Use this before submitting local files to check accepted file types, material options, confirmations, restrictions, and the private-upload flow. Does not calculate instant pricing. |
| find_recent_printable_filesA | Find recent local 3D print files in a project directory. Alias intents: find generated model, locate printable file, scan project for STL/STEP/3MF/OBJ/ZIP. Read-only and does not upload anything. |
| get_quote_statusA | Look up public-safe PrintYourDuck quote status using the quote request ID and matching customer email. Does not expose private file keys, payment URLs, supplier details, or sensitive operational data. |
| submit_local_file_for_quoteA | Upload one selected local 3D file privately and submit it for manual PrintYourDuck quote review. Alias intents: submit local model for quote, request manual print quote, upload generated 3D file. Requires explicit confirmations and user approval. No payment is collected and no instant price is returned. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct step in the quote workflow: requirements lookup, local file discovery, submission, and status retrieval. There is no functional overlap, and descriptions clearly reinforce the boundaries between read-only actions and the submission action.
All tool names follow a consistent verb_noun snake_case pattern with clear, distinct verbs (get, find, submit). Although some names are long, the naming style and structure are uniform.
Four tools is a well-scoped count for a focused manual quote request workflow. Each tool corresponds to a necessary step without redundancy or bloat.
The tool set covers the full quote request lifecycle: reading requirements, locating a printable file, submitting it for review, and checking status. There are no obvious missing operations that would create dead ends.