Skip to main content
Glama

Able.Style

Ways to Wear

style-ways-to-wear-by-id
Read-onlyIdempotent

Get outfit inspirations showing ways to wear a particular clothing item, including their tagged styles and owned userStyles. Uses the same selection logic as the Able.Style style page and requires sign-in. Copy exact IDs from earlier results: a ref with kind style uses styleId, and kind user_style uses userStyleId. Provide exactly one of styleId or userStyleId. Returns five items per page; the widget loads more on scroll. Without a widget, call this same tool again with only nextPageToken as pageToken when more results are wanted.

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": "style-ways-to-wear-by-id"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleIdNoExact catalog style ID. Omit userStyleId and pageToken.
pageTokenNoContinuation token from this tool. When supplied, omit all other inputs.
userStyleIdNoExact ID of a userStyle owned by the signed-in user. Omit styleId and pageToken.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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, closed-world), and the description adds substantial context beyond them: the sign-in requirement, the pagination contract (five items per page, widget auto-loads on scroll, re-call with only pageToken to continue), and the external selection logic it mirrors. This is exactly the extra behavioral detail annotations cannot carry.

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?

Purpose is front-loaded and the subsequent sentences each carry distinct operational content (auth, ID sourcing, exclusivity, pagination). It is dense but not padded; the only soft sentence is the vague reference to matching the Able.Style page's selection logic.

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?

With an output schema present, return values need no explanation, and the description still covers everything an agent needs to invoke correctly: auth, ID provenance, parameter exclusivity, and pagination. Nothing material is missing for this read-only lookup.

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 real meaning: the mutual-exclusion rule ('Provide exactly one of styleId or userStyleId') and the mapping from result refs to parameters (kind style → styleId, kind user_style → userStyleId). That tells the agent how to derive each ID, which the schema alone does not.

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?

The description names a specific verb and resource — 'Get outfit inspirations showing ways to wear a particular clothing item' — and scopes it further by noting the returned tagged styles and owned userStyles. It does not, however, distinguish itself from the similarly named sibling style-wear-with-get-by-id, leaving the agent to infer the difference between 'ways to wear' and 'wear with'.

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?

It states an auth precondition ('requires sign-in'), tells the agent where IDs must come from ('Copy exact IDs from earlier results'), and explains the continuation path for the no-widget case. It stops short of explicitly naming when a sibling tool would be the better choice, so it is clear context without exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources