within

What to wear with it

wear_with

Read-onlyIdempotent

Find clothes, shoes, bags, and accessories from independent luxury boutiques that go with a specific item, including prices, sizes, shop, and buy page for outfit ideas.

Instructions

The clothes, shoes, bags and accessories in stock at independent luxury boutiques that go with one item: the same ones its shopwithin.co page shows in its "Wear with" row. Each comes with the part of the outfit it is (the coat, the jeans, the bag), its price, the sizes in stock, the shop that has it and the page to buy it. Use this when someone asks what to wear with an item, how to style it, what goes with it, or wants outfit ideas built around something they found or bought here. Name the item by url, or by boutique_domain and id from another result. The url is a shopwithin.co product page link; the tool reads within's own catalog, documented at https://shopwithin.co/agents.

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": "wear_with"
  }
}

Input Schema

Name	Required	Description
`id`	No	The item's id from another result.
`url`	No	The item's shopwithin.co product page link, e.g. https://shopwithin.co/product/<boutique>/<words>/<id>.
`limit`	No	Most items to return, default 8.
`department`	No	For an item made for anyone: keep the row to women's or to men's. An item made for women or for men keeps its own.
`boutique_domain`	No	The item's boutique_domain from another result.

Output Schema

Name	Required	Description	Default
`item`	Yes
`note`	Yes
`found`	Yes
`pieces`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful operational context: results are limited to in-stock items and drawn from within's own catalog, with a documentation link. That is real added value beyond the annotations, but it stops short of richer traits such as how a missing or unresolvable item is handled.

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?

The first sentence front-loads the core purpose and the second adds return-field detail; nothing is padded or repetitive. The enumeration of returned attributes (the coat, the jeans, the bag, price, sizes, shop, buy page) somewhat overlaps with the output schema and could be trimmed, so it is not a perfect 5.

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?

With an output schema present and annotations covering safety, the description only needs to carry purpose, routing and input-identification semantics, all of which it does. It ties itself to a specific catalog representation and gives a documentation reference, leaving only edge-case behavior (unresolvable url, empty results) unstated.

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 goes beyond the schema by explaining that an item can be named either by url or by the boutique_domain plus id pair taken from another result, which clarifies the otherwise non-obvious fact that no single parameter is required but one of two identifying combinations is needed.

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 states a specific verb and resource: it returns complementary clothes, shoes, bags and accessories in stock at independent luxury boutiques for one given item, mirroring that item's "Wear with" row. This is a precise, well-scoped purpose an agent can grasp immediately. It does not explicitly differentiate itself from plausible siblings like similar_pieces or outfit_ideas, so it falls short of a 5.

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?

"Use this when someone asks what to wear with an item, how to style it, what goes with it, or wants outfit ideas built around something they found or bought here" gives clear situational triggers. However, it offers no when-not guidance and never names the alternatives (outfit_ideas, similar_pieces) that an agent would need to route correctly between them.

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