agentee-mcp

Search catalog

search_products

Read-onlyIdempotent

Find all-over-print tees in the allover.art catalog by free-text query, theme, style, color, section, and max price. Returns one card per design with price and URL, ranked by relevance.

Instructions

Search the allover.art catalog; returns one card per design (good_id, code, price, url) plus the total match count. Use it for any 'find me a …' request — list_collections is for curated themed pages, get_product for one card's sizes and fabrics. Filters combine: query is free text ('cat', 'neon koi'); theme is a canonical theme (Cats, Anime, Skulls; comma-separate several); style should follow the shopper's saved fit from get_user_prefs (basic → tee, oversized → oversized); max_price is USD. Ranked by relevance with a query, by best-sellers without. No paging: you get the top limit (default 24, max 48), so narrow the filters to reach the rest. Adult-only designs are excluded; an unknown color or style returns an error listing the valid values.

Input Schema

Name	Required	Description
`color`	No	Main color of the print.
`limit`	No	Max cards to return (default 24, max 48).
`query`	No	Free-text search, e.g. 'cat' or 'neon koi'.
`style`	No	Garment cut: tee, oversized, long_sleeve or oversized_long_sleeve.
`theme`	No	Canonical theme filter (Cats, Anime, Skulls, ...); comma-separate several.
`section`	No	Catalog section.
`max_price`	No	Only items priced at or below this amount, USD.

Output Schema

Name	Required	Description
`error`	No	Unknown color or style, with the valid values.
`items`	No	Product cards.
`total`	No	Total catalog matches for the filters.
`showing`	No	Number of cards returned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.2.0Oct 23, 2026

changedInput schema / properties / section / description

Previous value: -"Catalog section: mens, womens or kids."New value: +"Catalog section."

addedInput schema / properties / section / enum

Added value: +[
+  "mens",
+  "womens",
+  "kids"
+]

addedOutput schema / properties / error

Added value: +{
+  "description": "Unknown color or style, with the valid values.",
+  "type": "string"
+}

Changed2 schema fields changedv1.1.0Oct 23, 2026

addedInput schema / properties / color

Added value: +{
+  "description": "Main color of the print.",
+  "enum": [
+    "Black",
+    "Grey",
+    "White",
+    "Navy",
+    "Beige",
+    "Turquoise",
+    "Pink",
+    "Brown",
+    "Red",
+    "Purple",
+    "Olive",
+    "Blue",
+    "Green",
+    "Yellow",
+    "Orange",
+    "Burgundy",
+    "Multicolor"
+  ],
+  "type": "string"
+}

addedInput schema / properties / style

Added value: +{
+  "description": "Garment cut: tee, oversized, long_sleeve or oversized_long_sleeve.",
+  "enum": [
+    "tee",
+    "oversized",
+    "long_sleeve",
+    "oversized_long_sleeve"
+  ],
+  "type": "string"
+}

First observedOct 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already establish this as a read-only, idempotent, non-destructive search, but the description adds meaningful behavior beyond them: relevance ranking with a query versus best-sellers without, no paging, top-limit behavior with default 24 and max 48, adult-design exclusion, and error behavior for unknown colors or styles. These details materially help an agent predict results and failure modes.

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?

The description is dense but front-loaded: purpose and return shape come first, followed by sibling differentiation, filter behavior, ranking, paging constraints, and error handling. Every sentence carries operational information, and there is no redundant restatement of structured fields.

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?

For a 7-parameter search tool with an output schema and rich annotations, the description covers what an agent needs: return fields, ranking logic, limit behavior, filter combination, style selection from user preferences, and error cases. It is complete enough to invoke correctly without additional documentation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds useful semantics: query is free text with examples, theme is canonical and comma-separatable, style should be derived from the shopper's saved fit, and max_price is USD. It also clarifies that limit caps results at 48 and that narrowing filters is the only way to reach additional matches. Color semantics are left mostly to the schema, which keeps it from a full 5.

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 states a specific verb and resource ('Search the allover.art catalog') and clarifies the return shape: one card per design with good_id, code, price, and url plus total match count. It explicitly distinguishes this tool from list_collections and get_product, so an agent can select it without opening the schema.

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 gives explicit usage conditions ('find me a …' requests) and names alternatives: list_collections for curated themed pages and get_product for a single card's sizes/fabrics. It also explains how filters combine, how to choose style based on get_user_prefs, and how to work around the lack of paging by narrowing filters.

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