Skip to main content
Glama

printing-labs

by com.printinglabs
OverviewDiscussionsAdmin

search-products

Search Printing Labs' live corporate-gifting catalog (custom apparel, drinkware, welcome kits, bundles). Filter by free-text keyword, exact category, maximum unit price in INR, bundles only, or eco-friendly only. Every filter can be used alone, with no keyword. Returns matches with canonical product page URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results to return (default 8)
queryNoFree-text keyword matched against product names, categories, and descriptions. Optional — omit it to just apply the other filters.
ecoOnlyNoReturn only products/packs tagged eco-friendly (eco: true in the results)
categoryNoExact category name, e.g. 'Apparel & Headwear', 'Drinkware', 'Gourmet', 'Personal Accessories' — or a pack range, e.g. 'Festive & Diwali Packs', 'Welcome & Onboarding Packs'. list-product-categories returns both lists (`categories` and `bundleCategories`); only names from there match. There is no 'Environment friendly' category any more; use ecoOnly instead.
bundlesOnlyNoReturn only curated preset bundles / swag packs
maxPriceINRNoOnly products at or below this unit price in Indian Rupees

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Exact category name, e.g. 'Apparel & Headwear', 'Drinkware', 'Gourmet', 'Personal Accessories' — see list-product-categories for the full live list. There is no 'Environment friendly' category any more; use ecoOnly instead."New value: +"Exact category name, e.g. 'Apparel & Headwear', 'Drinkware', 'Gourmet', 'Personal Accessories' — or a pack range, e.g. 'Festive & Diwali Packs', 'Welcome & Onboarding Packs'. list-product-categories returns both lists (`categories` and `bundleCategories`); only names from there match. There is no 'Environment friendly' category any more; use ecoOnly instead."
  2. Changed3 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Exact category name, e.g. 'Apparel & Headwear', 'Drinkware', 'Gourmet', 'Personal Accessories' — see list-product-categories for the full live list"New value: +"Exact category name, e.g. 'Apparel & Headwear', 'Drinkware', 'Gourmet', 'Personal Accessories' — see list-product-categories for the full live list. There is no 'Environment friendly' category any more; use ecoOnly instead."
    • addedInput schema / properties / ecoOnly
      Added value: +{
+  "description": "Return only products/packs tagged eco-friendly (eco: true in the results)",
+  "type": "boolean"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Free-text keyword matched against product names, categories, and descriptions"New value: +"Free-text keyword matched against product names, categories, and descriptions. Optional — omit it to just apply the other filters."
  3. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Exact category name, e.g. 'Apparels', 'Drinkware', 'Gourmet', 'Environment friendly'"New value: +"Exact category name, e.g. 'Apparel & Headwear', 'Drinkware', 'Gourmet', 'Personal Accessories' — see list-product-categories for the full live list"
  4. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden; it discloses the return shape ('canonical product page URLs') and that any filter combination is valid, but says nothing about result ordering, pagination, or auth/rate-limit behavior for a live catalog query.

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?

Three sentences, front-loaded with the catalog scope, then filters, then output; little waste, though the filter enumeration partially duplicates what the schema already lists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter search with full schema coverage and no output schema, the description covers scope, valid filter dimensions, and return format adequately; only ordering/pagination details are absent, which is minor for this tool type.

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 schema already documents all six parameters in detail (including the eco-category migration note). The description restates the filter set and adds only the modest detail that each filter stands alone, meeting the baseline without exceeding it.

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 names a specific verb+resource ('Search Printing Labs' live corporate-gifting catalog') and enumerates the domain (custom apparel, drinkware, welcome kits, bundles), so an agent distinguishes this from sibling product tools like get-product-details or list-product-categories.

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

Usage Guidelines3/5

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

It clarifies that filters work independently and that the keyword is optional, which is useful usage context, but it never states when to prefer this over siblings such as list-product-categories or get-product-details, so alternatives are only implied.

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

All printing-labs 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