Skip to main content
Glama

Uwear

by ai.uwear
OverviewDiscussionsAdmin

List Garments

list_garments
Read-onlyIdempotent

List user's garments with structured filters or query for hybrid name/SKU/metadata/image-attribute search. body_zone expands to categories and is ORed with category when both are given. Garments may have no category. A category or body_zone filter excludes them unless include_uncategorized is true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
sortNoSort order: 'field:direction', e.g. 'created_at:desc', 'clothing_item_name:asc'. Default: created_at:desc
limitNoNumber of items per page
queryNoHybrid search across garment names, SKUs, metadata, and visual attributes.
tag_idsNoFilter to garments with any of these tags
categoryNoFilter to garments in any of these canonical categories; OR with body_zone when both are given.
end_dateNoFilter: created on or before this date (ISO format)
body_zoneNoFilter to categories in any of these body zones; OR with category when both are given.
start_dateNoFilter: created on or after this date (ISO format, e.g. '2025-06-01')
clothing_item_idsNoFilter to specific garment IDs
include_image_urlNoSet true when the garment image itself is needed for visual display or reuse.
include_uncategorizedNoAlso include garments with no category when category and/or body_zone filters are used.
exclude_clothing_item_idsNoExclude these garment IDs, for example the attached garment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / body_zone
      Added value: +{
+  "default": null,
+  "description": "Filter to categories in any of these body zones; OR with category when both are given.",
+  "items": {
+    "enum": [
+      "upper_body",
+      "lower_body",
+      "full_body",
+      "footwear",
+      "accessory",
+      "other"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / category / description
      Previous value: -"Filter to garments in any of these canonical categories"New value: +"Filter to garments in any of these canonical categories; OR with body_zone when both are given."
    • addedInput schema / properties / category / items / enum
      Added value: +[
+  "activewear",
+  "baby_and_childrens_clothing",
+  "blouses",
+  "bodysuits",
+  "cardigans",
+  "corset_tops",
+  "hoodies",
+  "overshirts",
+  "polos",
+  "shirts",
+  "sweaters",
+  "sweatshirts",
+  "t_shirts",
+  "tank_tops",
+  "tunics",
+  "dresses",
+  "lingerie",
+  "maternity_clothing",
+  "mens_undergarments",
+  "one_pieces",
+  "outerwear",
+  "outfit_sets",
+  "pants",
+  "shorts",
+  "skirts",
+  "skorts",
+  "sleepwear_and_loungewear",
+  "socks",
+  "suits",
+  "swimwear",
+  "traditional_and_ceremonial_clothing",
+  "uniforms_and_workwear",
+  "wedding_and_bridal_party_dresses",
+  "clothing_accessories",
+  "costumes_and_accessories",
+  "handbag_and_wallet_accessories",
+  "handbags_wallets_and_cases",
+  "jewelry",
+  "shoe_accessories",
+  "shoes",
+  "other"
+]
    • addedInput schema / properties / exclude_clothing_item_ids
      Added value: +{
+  "default": null,
+  "description": "Exclude these garment IDs, for example the attached garment.",
+  "items": {
+    "type": "integer"
+  },
+  "maxItems": 100,
+  "type": "array"
+}
    • addedInput schema / properties / include_uncategorized
      Added value: +{
+  "default": false,
+  "description": "Also include garments with no category when category and/or body_zone filters are used.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / category
      Added value: +{
+  "default": null,
+  "description": "Filter to garments in any of these canonical categories",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only and idempotent behavior. The description adds meaningful behavioral context beyond annotations, such as the OR logic between body_zone and category, the expansion of body_zone to categories, and the exclusion of uncategorized garments unless include_uncategorized is true. These are non-obvious behaviors not fully evident from schema alone.

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 with no redundancy. The first states the core purpose, the second explains the body_zone/category interaction, and the third addresses the uncategorized edge case. All content is essential and front-loaded.

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?

The description covers the key filtering semantics and edge cases. While it doesn't describe the return format, the tool's name and read-only annotations imply a list of garments. Pagination and sorting are documented in the schema, so the description does not need to repeat them. The description is sufficiently complete for a list tool with no output schema.

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. The description adds value by clarifying the relationship between body_zone and category (ORed, expansion) and the uncategorized handling, which is not fully explicit in the schema. This improves parameter understanding beyond the individual descriptions.

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 clear verb and resource ('List user's garments') and distinguishes itself by detailing the hybrid search and structured filter capabilities. It differentiates from siblings like get_garment (single item) and get_items_by_tag (tag-specific) by implying this is the general listing tool with advanced filtering.

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?

The description implies usage as the primary garment listing tool but does not explicitly contrast it with alternatives like get_items_by_tag or get_garment. It provides context for when to use it (e.g., when needing structured filters or hybrid search) but lacks explicit exclusionary guidance.

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

All Uwear 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