Project Tango

List All Products

list_all_products

Browse or search the product catalog by category, price range, or free-text query to find items by name, SKU, description, or tag for recommendations, restocking, or copywriting.

Instructions

Returns the product catalog, optionally filtered by category, a min/max price range, or a free-text search. Use this to browse inventory or to find a specific product by name, SKU, description or tag before recommending, restocking, or drafting copy for products.

Input Schema

TableJSON Schema

Name	Required	Description
`search`	No	Free-text search matched against product name, SKU, description, tags and category. Case-insensitive substring, so 'merino' finds the Highland Merino Wool Sweater. Results are ranked by match quality, so a product whose own name or tag is the query comes first; the set of matches is the same either way. Combine with the other filters to narrow further.
`category`	No	Restrict results to a single category, e.g. 'tech', 'apparel', or 'home'. Case-insensitive. Omit to include all categories.
`max_price`	No	Only include products priced at or below this amount, in USD.
`min_price`	No	Only include products priced at or above this amount, in USD.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`filters`	Yes
`products`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.2.0Oct 7, 2026

changedInput schema / properties / search / description

Previous value: -"Free-text search matched against product name, SKU, description, tags and category. Case-insensitive substring, so 'merino' finds the Highland Merino Wool Sweater. Combine with the other filters to narrow further."New value: +"Free-text search matched against product name, SKU, description, tags and category. Case-insensitive substring, so 'merino' finds the Highland Merino Wool Sweater. Results are ranked by match quality, so a product whose own name or tag is the query comes first; the set of matches is the same either way. Combine with the other filters to narrow further."

First observedv3.0.1Oct 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It conveys that filters are optional and that the unfiltered default returns the whole catalog, which is useful, but says nothing about result size, pagination, ordering guarantees beyond what the schema already states, or permissions. Adequate but thin for a no-annotation tool.

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?

Two sentences, front-loaded with the return behavior and then the use cases; no filler or repetition. The second sentence is somewhat long with a four-item enumeration, but each item (recommending, restocking, drafting copy) maps to real sibling workflows and earns its place.

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?

With a 100%-covered schema and an output schema present, the description need not restate parameters or return shape, and it correctly delegates those. What remains missing is only the low-risk behavioral profile (read-only, no side effects, result volume) for a tool with no annotations, which is a minor gap given the obvious read semantics of 'Returns'.

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% and the search parameter's ranking/substring semantics are fully documented in the schema, so the baseline is 3. The description only summarizes the filter categories ('category, a min/max price range, or a free-text search') without adding syntax, defaults, or combination behavior beyond what the schema already provides.

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+resource ('Returns the product catalog') and enumerates the available filters, so the agent knows exactly what this tool produces. It does not name or contrast with any sibling (e.g. find_orders, get_low_stock_alerts), so differentiation is inferred from the resource noun rather than stated.

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?

Gives clear usage context: browse inventory or locate a product by name/SKU/description/tag, and lists downstream scenarios (recommending, restocking, drafting copy) that motivate the call. No explicit when-not-to-use or alternative-tool routing is provided, so it stops short of a 5.

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

Deploy Server