Printdash

List Printdash products

list_products

Read-onlyIdempotent

Every product Printdash sells (business cards, flyers, stickers, labels, booklets, signs, banners and more), with its id, a one-line description, its page and from_price: the starting price the site shows ("From $X inc GST for N", public retail for the product's default job). Start here or with search_products. A from_price is a guide only: price_job gives the exact price of the customer's job. Printdash prints in Australia and delivers within Australia only; prices are in AUD and include GST.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`next`	Yes
`count`	Yes
`currency`	Yes
`delivery`	Yes
`products`	Yes
`service_area`	Yes
`from_price_note`	Yes
`prices_include_gst`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedOutput schema / properties / products / items / properties / from_price / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "priced_at": {
-        "description": "When Printdash's pricing service priced it for the site.",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "quantity": {
-        "description": "How many the starting price is for.",
-        "type": "number"
-      },
-      "total_inc_gst": {
-        "description": "AUD including GST, public retail, for the product's default_configuration at quantity.",
-        "type": "number"
-      }
-    },
-    "required": [
-      "total_inc_gst",
-      "quantity",
-      "priced_at"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "priced_at": {
+        "description": "When Printdash's pricing service priced it for the site.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "quantity": {
+        "description": "How many the starting price is for.",
+        "type": "number"
+      },
+      "source": {
+        "description": "site: the figure printdash.io publishes now; bundled: the same figure as of Printdash's last server update.",
+        "enum": [
+          "site",
+          "bundled"
+        ],
+        "type": "string"
+      },
+      "total_inc_gst": {
+        "description": "AUD including GST, public retail, for the product's default_configuration at quantity.",
+        "type": "number"
+      }
+    },
+    "required": [
+      "total_inc_gst",
+      "quantity",
+      "priced_at",
+      "source"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world. Beyond that, the description discloses that from_price is an indicative starting price for the default job only, that prices are AUD and GST-inclusive, and that delivery is Australia-only — useful context an agent would otherwise get wrong.

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-loads the resource and returned fields, then the routing hint, then the pricing caveat and geography. Dense but every sentence carries information; the parenthetical price gloss is slightly verbose.

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?

An output schema exists so return values need not be explained, yet the description still frames what they mean (from_price semantics) plus currency, tax, and delivery scope — everything an agent needs to call this correctly and interpret the result.

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?

Zero parameters, so the baseline is 4. The description instead characterizes the returned fields and the meaning of from_price, which is more than the empty schema provides.

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?

Names a specific verb+resource (every product Printdash sells) and enumerates the catalog categories, then states the fields returned (id, description, page, from_price). It distinguishes itself from search_products by positioning as a full-catalog starting point.

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

Usage Guidelines4/5

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

"Start here or with search_products" gives an explicit alternative entry point, and "price_job gives the exact price of the customer's job" routes pricing questions elsewhere. It stops short of saying when search is preferred over list (e.g., when the catalog is unknown or large).

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

All Printdash 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?