Skip to main content
Glama
sfsupplies

product-search-mcp-server

by sfsupplies

search_products

Search the SF Supplies product catalog for vinyl, films, and signage supplies. Use free-text queries or filter by attributes, stock, and product status to find products with availability information.

Instructions

Search the SF Supplies product catalog (vinyl, films, signage supplies, etc.). Returns matching products with their name, page URL, stock status, product status, and attributes (Brand, Color, Size, Material, Finish, Series, …). Use the optional 'filters' to narrow by attribute — call list_product_filters first if you need to know which attributes/values are available. Two distinct availability signals: 'in stock' reflects inventoryQty — whether the item is ACTUALLY in stock in the warehouse right now (yes/no). 'status' is the catalog classification: StockItem (normally stocked), InHouse (made/held in house), NonStock (orderable, not stocked), Discontinued (no longer offered), Development (not yet released), or Null. A product can be a StockItem yet currently out of stock — when asked about availability, use 'in stock' (inventoryQty), not 'status'. To FILTER by these, pass 'in_stock' (true = only in-stock, false = only out-of-stock) and/or 'product_status'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoZero-based page index (default 0).
searchYesFree-text query, e.g. 'Avery translucent vinyl'. May be empty to browse by filters/category alone.
filtersNoAttribute filters to narrow results. Keys are facet field names (see list_product_filters), values are arrays of allowed values, e.g. {"Brand": ["Avery"], "Color": ["Plum"], "Size": ["15\" x 10 Yards"]}. Multiple values for one field are OR-ed; different fields are AND-ed.
in_stockNoFilter by real warehouse availability: true = only items currently in stock, false = only out-of-stock. Omit to include both.
page_sizeNoResults per page (1-50, default 8).
sort_columnNoColumn to sort by (optional; leave empty for relevance).
category_slugNoRestrict to a category by its slug (optional).
product_statusNoFilter to one catalog status (StockItem, InHouse, NonStock, Discontinued, Development). Omit for all. Distinct from in_stock — a StockItem can be out of stock.
sort_directionNo'asc' or 'desc' (optional).
Behavior4/5

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

No annotations, so description carries full burden. Explains two availability signals ('in stock' vs. 'product status'), filter semantics, and that empty search browses. Lacks details on rate limits, auth, or pagination behavior.

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?

While informative, the description is a single dense paragraph. Could be more scannable with bullet points or sections, but sentences are purposeful and front-loaded with purpose.

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?

Given 9 parameters, 100% schema coverage, no output schema, and two siblings, the description is comprehensive. Covers filter mechanics, stock/status distinction, and suggests a prerequisite tool. Minor omission: no mention of sort behavior or pagination beyond defaults.

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

Parameters5/5

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

Schema coverage is 100%, yet description adds significant value: explains filters structure with examples, clarifies in_stock and product_status enum meanings, and notes default values. Goes well beyond bare schema.

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?

Explicitly states it searches the SF Supplies product catalog, lists return fields, and distinguishes stock vs. status. Mentions sibling tool list_product_filters for attribute discovery.

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?

Advises calling list_product_filters first for available attributes, explains when to use in_stock vs. product_status, and clarifies filter logic (OR/AND). Does not explicitly contrast with suggest_products.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sfsupplies/internal-product-search-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server