Skip to main content
Glama

InkFE Print

by com.inkfe
OverviewDiscussionsAdmin

Search InkFE products

search_products
Read-onlyIdempotent

Search the public InkFE print catalog by free text. Use this when the buyer wants something other than a business card, or to confirm a product exists before calling get_product. Returns up to limit products with handle, title, productType, priceRange (min/max pack price and currency), the customer-facing options with their allowed values, and the product page URL. Pass the returned handle to get_product for variants and dimensions. Optional productType, templateCompatibleOnly and availableOnly filters narrow discovery. Each result distinguishes catalog visibility from template support; failed detail reads are explicitly unavailable. Prices are not quotes. Business cards designed from a template do not need this tool: list_business_card_templates already reports the productHandle to buy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of products to return (1-20, default 10).
queryYesFree-text search over the public InkFE catalog, matched against product titles, types and tags (for example "business cards", "poster", "greeting card").
productTypeNoOptional exact productType filter from catalog results, case-insensitive.
availableOnlyNoOnly products with at least one currently purchasable variant.
templateCompatibleOnlyNoOnly products compatible with this MCP's verified business-card template journey. Does not enable writes on a catalog-only endpoint.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesWhere the catalog data comes from and how fresh it is.
nextStepYes
productsYesMatching public products, in catalog order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "nextStep": {
+      "type": "string"
+    },
+    "products": {
+      "description": "Matching public products, in catalog order.",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "artwork": {
+            "additionalProperties": {},
+            "description": "Which InkFE artwork and checkout actions this product supports.",
+            "properties": {
+              "checkout": {
+                "enum": [
+                  "shopify_hosted",
+                  "unavailable"
+                ],
+                "type": "string"
+              },
+              "designAvailable": {
+                "description": "Whether design tools can be used for this product here.",
+                "type": "boolean"
+              },
+              "mode": {
+                "enum": [
+                  "business_card_template",
+                  "catalog_only"
+                ],
+                "type": "string"
+              },
+              "nextStep": {
+                "type": "string"
+              },
+              "templateCompatible": {
+                "description": "True only for the configured business-card product the template journey supports.",
+                "type": "boolean"
+              },
+              "unsupportedActions": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              }
+            },
+            "required": [
+              "templateCompatible",
+              "mode",
+              "designAvailable",
+              "checkout",
+              "unsupportedActions",
+              "nextStep"
+            ],
+            "type": "object"
+          },
+          "detailStatus": {
+            "description": "unavailable means the product detail read failed.",
+            "enum": [
+              "available",
+              "unavailable"
+            ],
+            "type": "string"
+          },
+          "handle": {
+            "description": "Pass this to get_product.",
+            "type": "string"
+          },
+          "image": {
+            "anyOf": [
+              {
+                "additionalProperties": {},
+                "properties": {
+                  "altText": {
+                    "type": "string"
+                  },
+                  "url": {
+                    "description": "Public Shopify CDN image URL.",
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "url",
+                  "altText"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Example product image, not a customer proof."
+          },
+          "options": {
+            "items": {
+              "additionalProperties": {},
+              "properties": {
+                "name": {
+                  "type": "string"
+                },
+                "values": {
+                  "items": {
+                    "type": "string"
+                  },
+                  "type": "array"
+                }
+              },
+              "required": [
+                "name",
+                "values"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "priceRange": {
+            "additionalProperties": {},
+            "description": "Pack price range; catalog prices are not a quote.",
+            "properties": {
+              "currency": {
+                "type": "string"
+              },
+              "max": {
+                "type": "string"
+              },
+              "min": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "min",
+              "max",
+              "currency"
+            ],
+            "type": "object"
+          },
+          "productType": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "summary": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "description": "Public product page URL.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "handle",
+          "title",
+          "productType",
+          "priceRange",
+          "options",
+          "url",
+          "detailStatus",
+          "summary",
+          "image",
+          "artwork"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "source": {
+      "additionalProperties": {},
+      "description": "Where the catalog data comes from and how fresh it is.",
+      "properties": {
+        "authority": {
+          "type": "string"
+        },
+        "details": {
+          "type": "string"
+        },
+        "discoveryRevalidateSeconds": {
+          "type": "number"
+        },
+        "pricing": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "authority",
+        "discoveryRevalidateSeconds",
+        "details",
+        "pricing"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "products",
+    "source",
+    "nextStep"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false curve the safety profile. The description adds valuable behavioral context: results are capped at `limit`, prices are 'not quotes', templateCompatibleOnly 'does not enable writes on a catalog-only endpoint', and failed detail reads are explicitly unavailable. No contradiction with annotations.

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?

The description is dense but not bloated: it front-loads the usage trigger)Skip then packs in result contents, downstream handoff to get_product, filters, pricing caveat, and sibling differentiation. Every sentence carries relevant information, with negligible redundancy.

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?

Given the output schema and full parameter documentation, the description covers the remaining decision-critical context: when to use it, when not to, how to continue to get_product, what results mean, and the non-quote nature of prices. An agent can select and invoke this tool correctly with the information provided.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3 and the description does not need to compensate. It reinforces the purpose of filters and `limit`, but the schema already provides detailed parameter semantics, so the description adds little beyond what is structured.

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?

The description specifies a concrete verb and resource: 'Search the public InkFE print catalog by free text.' It also differentiates itself from siblings by naming get_product and list_business_card_templates and explaining how they relate.

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?

It explicitly says when to use the tool: 'Use this when the buyer wants something other than a business card, or to confirm a product exists before calling get_product.' It also states an exclusion: business cards designed from a template should instead use list_business_card_templates.

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

All InkFE Print 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