Skip to main content
Glama
Sign In

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. With a category or body_zone filter and include_uncategorized=false, uncategorized_count reports garments hidden by the category filter within the same scope. If matches are short and uncategorized_count > 0, call again with include_uncategorized=true and inspect those garments.

Input 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. If the first result has uncategorized_count > 0 and too few matches, call again with true and inspect those garments.
exclude_clothing_item_idsNoExclude these garment IDs, for example the attached garment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / include_uncategorized / description
      Previous value: -"Also include garments with no category when category and/or body_zone filters are used."New value: +"Also include garments with no category when category and/or body_zone filters are used. If the first result has uncategorized_count > 0 and too few matches, call again with true and inspect those garments."
  2. 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"
+}
  3. 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"
+}
  4. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare the generic safety profile (readOnly, idempotent, non-destructive), so the description carries the real behavioral load. It discloses the OR semantics between body_zone and category, the scoping rule that uncategorized_count only reports when a category/body_zone filter is active with include_uncategorized=false, and the recovery workflow. Since there is no output schema, surfacing uncategorized_count behavior here is genuinely necessary.

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?

Four sentences, front-loaded with the core purpose, then filter semantics, then the follow-up rule. No filler or repetition of schema text. It is somewhat dense for a single paragraph, but every sentence carries a distinct operational fact.

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 13-parameter, zero-required read tool with no output schema, the description covers the non-obvious interactions (category/body_zone OR, uncategorized handling) that an agent would otherwise get wrong. Pagination, sorting and ID filters are adequately covered by the schema. The main omission is what the response shape looks like beyond uncategorized_count, though that is defensible without an 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 description coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: body_zone 'expands to categories' (expanding rather than exact-matching), the OR relationship with category, and the conditional semantics of include_uncategorized and uncategorized_count. That is real added value over the per-field schema text.

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 ('List user's garments') and immediately distinguishes two modes: structured filters versus hybrid name/SKU/metadata/image-attribute search. It does not, however, name the closest sibling (e.g. search_uwear_library or list_outfits) to route the agent between them, so the differentiation is functional rather than sibling-aware.

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 concrete conditional guidance: body_zone ORs with category when both are supplied, and it prescribes an explicit follow-up ('If matches are short and uncategorized_count > 0, call again with include_uncategorized=true'). That is unusually actionable for a list tool. It stops short of stating when to prefer this tool over the sibling list/search tools.

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