Skip to main content
Glama

Printdash

by io.printdash
OverviewDiscussionsAdmin

Search Printdash products

search_products
Read-onlyIdempotent

Finds the Printdash products that match the customer's words ("A5 flyers", "round stickers", "pull up banner"), best first. Returns ids for get_product, each with the site's from_price (a starting price; price_job gives the exact one). Printdash prints in Australia and delivers within Australia only; prices are in AUD and include GST.

Input Schema

NameRequiredDescriptionDefault
queryYesThe customer's words for what they want printed.

Output Schema

NameRequiredDescriptionDefault
nextYes
countYes
queryYes
currencyYes
productsYes
service_areaYes
from_price_noteYes
prices_include_gstYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world. The description adds real value beyond them: results are relevance-ranked, from_price is a 'starting price' rather than the final one, and the service is Australia-only with AUD prices including GST. It omits what happens on no matches or any result cap, which keeps it 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with the primary action and ranking front-loaded, followed by the id/price chain and then regional/currency caveats. No sentence repeats the name or the schema.

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?

For a single-parameter search tool with full schema coverage, annotations for safety, and an output schema for return shape, the description covers everything else an agent needs: relevance ordering, the meaning of from_price versus price_job, and geographic/currency constraints.

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 100% and the schema already defines query as 'the customer's words', so baseline is 3. The description earns one more by reinforcing that the input should be natural customer phrasing and giving concrete examples ('A5 flyers', 'round stickers', 'pull up banner') that demonstrate acceptable granularity.

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 ('Finds the Printdash products'), scopes the input to customer language, and shows the ranking behavior ('best first'). The example queries and the note that it returns ids for get_product separate it clearly from list_products and get_product.

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?

Implies the trigger condition well: use it when the customer describes what they want in their own words, then feed the returned id to get_product and use price_job for exact pricing. It never explicitly excludes browsing all products via list_products, so the alternative case is left implicit.

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

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