Skip to main content
Glama
Sign In

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search-products"
  }
}

Input 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 / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. 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."
  3. 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."
  4. 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"
  5. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It discloses that the catalog is live and that results include canonical product page URLs, and "Search" implies a non-mutating read, but it says nothing about result limits/pagination behavior, whether pricing is company-specific, or any access constraints.

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 sentences, front-loaded with what is searched, then the filter model, then the return shape. No filler or repetition; each sentence carries distinct information.

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 six-parameter, fully optional, read-only search tool with complete schema documentation and no output schema, the description covers purpose, filter combinability, and the shape of returned URLs. Only minor gaps remain around result limits and whether prices are company-specific, which the schema partly mitigates.

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 explains each filter, including exact-category naming, the removed "Environment friendly" category, and default limit. The description restates the filter list and adds only the general rule that any filter works without a keyword — modest value beyond structured data, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — "Search Printing Labs' live corporate-gifting catalog" — and enumerates the covered content types (apparel, drinkware, kits, bundles), which separates it from detail-oriented siblings like get-product-details. It stops short of explicitly naming a sibling it supersedes or is superseded by, so it is clear but not fully differentiated.

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?

"Every filter can be used alone, with no keyword" gives concrete invocation guidance, and the category parameter points the agent at list-product-categories for valid values. There is no explicit when-not-to-use statement or pointer to get-product-details for full record retrieval, so the routing guidance is clear but incomplete.

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