Able.Style

Search Wardrobe

search_wardrobe

Read-onlyIdempotent

Use this when the user wants to browse or search their signed-in wardrobe, including questions about categories, colours, attributes, newest items, and natural-language terms such as 'flowery shirts'. Returns up to five items per call and the total number of matches across all pages. The results widget automatically loads further pages as the user scrolls. If the widget is unavailable and nextPageToken is present, call this tool again with only that pageToken when the user asks for more results. Do not combine a pageToken with query, sortBy, or filters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_wardrobe"
  }
}

Input Schema

Name	Required	Description
`query`	No	Optional natural-language wardrobe search. Whitespace is trimmed.
`sortBy`	No	Sort order. Defaults to relevance for a query and newest-first without a query.
`filters`	No
`pageToken`	No	Opaque continuation token from the preceding result. When supplied, omit all other inputs.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds real behavior: a five-item page size, a total match count, widget-driven auto-pagination, and the nextPageToken fallback procedure. The explicit constraint not to combine pageToken with query/sortBy/filters is exactly the kind of operational rule structured fields cannot convey.

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?

Front-loaded with purpose, then pagination mechanics, with no filler sentences. The pagination paragraph is slightly dense but each clause governs a distinct call pattern (widget vs. manual token), so it earns its place.

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?

An output schema exists, so return values need not be spelled out, yet the description supplies cardinality and pagination semantics anyway. Combined with the conflict rule and the nested-filter hint (attribute requires itemType.category), an agent has everything needed to call this correctly.

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 75% and the schema already documents parameter formats, so the baseline is 3. The description still adds value by illustrating natural-language query semantics ('flowery shirts'), clarifying the pageToken-alone rule, and implying the interaction between 'newest items' and sortBy.

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?

States a specific verb+resource ('browse or search their signed-in wardrobe') and enumerates the queryable dimensions (categories, colours, attributes, newest items, natural-language terms). This is clearly distinguishable from the add/remove/outfit siblings, which perform writes rather than retrieval.

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?

Opens with an explicit when-to-use trigger ('when the user wants to browse or search their signed-in wardrobe') and includes concrete query examples. It does not name or exclude a specific alternative sibling, but the sibling set is so operationally distinct (add/remove/style) that exclusion is not strictly needed.

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

All Able.Style tools Inspect

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

Need Help?